Message152470
| Author |
roger.serwy |
| Recipients |
Jeroen, pje, roger.serwy, terry.reedy |
| Date |
2012年02月02日.17:42:57 |
| SpamBayes Score |
2.1843427e-07 |
| Marked as misclassified |
No |
| Message-id |
<1328204584.48.0.0303985386466.issue13926@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
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 pydoc itself.
Steps to reproduce:
>>> help()
help> modules
-- stall --
A blank "Tk" window suddenly appeared, which suggested that something loaded Tkinter. Digging deeper, the "help" utility in Lib/pydoc.py loads every single module found on in sys.path in order to get its __doc__ string. This is doing too much work as the purpose of "modules" is to give a list of available modules.
I modified "ModuleScanner" in pydoc.py so that loader.load_module doesn't get called. I set "desc" and "path" do hard-coded strings and now "modules" returns a list very quickly. A blank tkinter window still pops up, however. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年02月02日 17:43:04 | roger.serwy | set | recipients:
+ roger.serwy, terry.reedy, pje, Jeroen |
| 2012年02月02日 17:43:04 | roger.serwy | set | messageid: <1328204584.48.0.0303985386466.issue13926@psf.upfronthosting.co.za> |
| 2012年02月02日 17:42:58 | roger.serwy | link | issue13926 messages |
| 2012年02月02日 17:42:57 | roger.serwy | create |
|