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 loewis
Recipients loewis, yappie
Date 2010-06-24.22:43:53
SpamBayes Score 0.005359826
Marked as misclassified No
Message-id <1277419435.1.0.961927616813.issue9072@psf.upfronthosting.co.za>
In-reply-to
Content
This is not a bug. You didn't *nearly* reset Python to the state in which it was before the import: the modules that got imported recursively still hang in sys.modules.

Please accept that Python indeed does not support unloading modules for severe, fundamental, insurmountable, technical problems, in 2.x.

In 3.x, chances are slightly higher. In principle, unloading could be supported - but no module actually adds the necessary code, and the necessary code in the import machinery isn't implemented in 3.2 and earlier.

Supporting unloading will be (and was) a multi-year project. Don't expect any results in the next five years.
History
Date User Action Args
2010-06-24 22:43:55loewissetrecipients: + loewis, yappie
2010-06-24 22:43:55loewissetmessageid: <1277419435.1.0.961927616813.issue9072@psf.upfronthosting.co.za>
2010-06-24 22:43:53loewislinkissue9072 messages
2010-06-24 22:43:53loewiscreate