I'm having the same problem. The problem seems to be that
help(modules) iterates through all the modules, loading each one in
turn, and if any one of them is broken then the iteration will fail,
without a sensible indication of where the failure occurred.
As an alternative method of listing all
Jeroen dario...@gmail.com added the comment:
Ned,
I've run the help() from the command-line as requested and the result was:
Python 2.7.2+ (default, Oct 4 2011, 20:06:09)
[GCC 4.6.1] on linux2
Type help, copyright, credits or license for more information.
help()
Welcome to Python 2.7! This
Ned Deily n...@acm.org added the comment:
Thanks for the additional output. It demonstrates that the problem you've
encountered is an old known issue with pydoc help when there are modules that
cause exceptions upon importing. And the additional issue Roger brought up is
also due to pydoc
Ned Deily n...@acm.org added the comment:
Jeroen, if you try running help() from a command-line python2.7, rather than
in IDLE, what results do you get? Most likely, Python will crash there and
there should be an exception and traceback printed, in which case the problem
has nothing to do
Changes by Terry J. Reedy tjre...@udel.edu:
--
superseder: Clarify sentence in tutorial - help(modules) executes module code
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13926
___
Terry J. Reedy tjre...@udel.edu added the comment:
digit transposition corrected 12902
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13926
___
Roger Serwy roger.se...@gmail.com added the comment:
I tried this and while IDLE didn't crash, it stalled when running with and
without a subprocess. I then tried running this from the regular python
interpreter and it stalled there as well. This is not a problem with IDLE, but
a problem with
Phillip J. Eby p...@telecommunity.com added the comment:
The problem might be that you're iterating over more than just the top
level; if you look for submodules then the parent package has to be
imported... and that might make that window load, if there's module-level
code in the package
Roger Serwy roger.se...@gmail.com added the comment:
Should calling modules automatically iterate over all submodules or should it
return just a list of top level modules?
--
___
Python tracker rep...@bugs.python.org
Phillip J. Eby p...@telecommunity.com added the comment:
I don't have the code you're talking about in front of me; just wanted to
give you a lead on the likely cause.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13926
Roger Serwy roger.se...@gmail.com added the comment:
You're right. The pkgutil.walk_packages method called from ModuleScanner seems
to be importing the submodules. I should have said that in the last message.
I'll try to be clearer. What should the correct behavior be when entering
modules in
Terry J. Reedy tjre...@udel.edu added the comment:
This issue is essentially a duplicate of #12092. For the OP there, the stall
happens because something on Gnome pops up a configuration GUI and, I presume,
waits for response. I am thinking now that 'modules' is simply a bad idea and
should
12 matches
Mail list logo
