claudio.grondi at freenet.de
Thu Nov 17 13:49:41 CET 2005
Here a correction of the code snippet:
# making additional modules available in IDLE directly after
re-start of it:
self.runsource("import os; from path import path")
# restart subprocess debugger
I have no slightest idea why does it make a difference.
What would make much more sense for me is to wait until
but this resulted in an endless loop ...
"Claudio Grondi" <claudio.grondi at freenet.de> schrieb im Newsbeitrag
news:3u3899Fv3vulU1 at individual.net...
> <bobueland at yahoo.com> schrieb im Newsbeitrag
> news:1132225335.948524.162190 at g43g2000cwa.googlegroups.com...
> > I did as you suggested, however
> > after I make a new File (File/New Window) and save and then run (F5) I
> > get the following alert
> > The Python Shell is already executing a command; please waith until it
> > is finished
> > I also get the error message
> > Traceback (most recent call last):
> > File "<pyshell#1>", line 1, in -toplevel-
> > import os; from path import path
> > ImportError: No module named path
> > >>>
> > Bob
> Sure you have to replace "import os; from path import path"
> with " from btools import *", than you avoid the error message
> but not the problem you have got with the message box.
> A "solution" to the problem with the message box may be as follows:
> # restart subprocess debugger
> # (-Patch)
> # making additional modules available in IDLE directly after
> re-start of it:
> self.runsource("import os; from path import path")
> # (Patch-)
> if debug:
> If 0.1 doesn't work on your system, just increase the value, but this will
> delay the response.
> e.g. 0.001 doesn't work for me, but 0.1 does (Intel Pentium 4 running at
More information about the Python-list