This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author samwyse
Recipients samwyse
Date 2009-06-22.05:30:16
SpamBayes Score 2.1276435e-07
Marked as misclassified No
Message-id <1245648620.51.0.901061764952.issue6321@psf.upfronthosting.co.za>
In-reply-to
Content
Every time IDLE is asked to run a program, it doesn't ensure that the 
modules referenced by the program are completely loaded.  This can cause 
problems if one of those modules is also being edited, because once it 
is loaded, any subsequent changes are not compiled and re-loaded.  
PyUnit faced a similar problem and solved it with a custom importer 
(http://pyunit.sourceforge.net/notes/reloading.html).  Ideally, the 
custom importer would be used in two places:  The obvious choice is when 
a program is run, unloading when it returns.  The less obvious is when 
the Python Shell window is opened, since import statements can be run 
from there as well.  Closing that window should cause all such imports 
to be unloaded.  Of course, care must be taken to insure that all run 
commands are properly nested within the lifetime of a shell window.
History
Date User Action Args
2009-06-22 05:30:21samwysesetrecipients: + samwyse
2009-06-22 05:30:20samwysesetmessageid: <1245648620.51.0.901061764952.issue6321@psf.upfronthosting.co.za>
2009-06-22 05:30:18samwyselinkissue6321 messages
2009-06-22 05:30:16samwysecreate