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 ncoghlan
Recipients brett.cannon, eli.bendersky, ezio.melotti, flox, ncoghlan
Date 2012-02-17.03:45:22
SpamBayes Score 8.548142e-10
Marked as misclassified No
Message-id <1329450324.01.0.775157062672.issue14035@psf.upfronthosting.co.za>
In-reply-to
Content
Keeping module references implicitly in import_fresh_module will leak references like crazy in the test suite. The onus is on the code referencing module contents to ensure that the module globals remain valid.

If we get rid of the explicit clearing of module globals to break reference cycles, this problem will also go away, so closing as a dupe of #812369.
History
Date User Action Args
2012-02-17 03:45:24ncoghlansetrecipients: + ncoghlan, brett.cannon, ezio.melotti, eli.bendersky, flox
2012-02-17 03:45:24ncoghlansetmessageid: <1329450324.01.0.775157062672.issue14035@psf.upfronthosting.co.za>
2012-02-17 03:45:22ncoghlanlinkissue14035 messages
2012-02-17 03:45:22ncoghlancreate