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 yappie
Recipients loewis, yappie
Date 2010-06-24.23:34:48
SpamBayes Score 0.0016966
Marked as misclassified No
Message-id <AANLkTikhWS2FRqELSIXvn8wjE-XgTKJGMIJCwVTQMEy_@mail.gmail.com>
In-reply-to <1277419435.1.0.961927616813.issue9072@psf.upfronthosting.co.za>
Content
Thank you for taking time to answer my question about unloading modules.
I really appreciate it!

Slava

On Fri, Jun 25, 2010 at 2:43 AM, Martin v. Löwis <report@bugs.python.org>wrote:

>
> Martin v. Löwis <martin@v.loewis.de> added the comment:
>
> 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.
>
> ----------
> nosy: +loewis
> resolution:  -> wont fix
> status: open -> closed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue9072>
> _______________________________________
>
Files
File name Uploaded
unnamed yappie, 2010-06-24.23:34:48
History
Date User Action Args
2010-06-24 23:34:51yappiesetrecipients: + yappie, loewis
2010-06-24 23:34:49yappielinkissue9072 messages
2010-06-24 23:34:49yappiecreate