Nick Coghlan <ncogh...@gmail.com> added the comment: 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. ---------- resolution: -> duplicate status: open -> closed superseder: -> module shutdown procedure based on GC _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue14035> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
