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 r.david.murray
Recipients Terry Garyet, r.david.murray
Date 2015-11-13.19:41:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1447443686.75.0.623680718477.issue25619@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, python2 shutdown has this problem: modules and their attributes are set to None during interpreter shutdown.  Things are much better in python3.  If you want to avoid the error messages, finalize the objects explicitly (making sure to break gc cycles) before the end of your program, or keep explicit references to the objects you need during __del__ (eg: os_path = os.path in the global scope of your module).

As for your last comment, you are correct, the GC cleanup order is not deterministic.
History
Date User Action Args
2015-11-13 19:41:26r.david.murraysetrecipients: + r.david.murray, Terry Garyet
2015-11-13 19:41:26r.david.murraysetmessageid: <1447443686.75.0.623680718477.issue25619@psf.upfronthosting.co.za>
2015-11-13 19:41:26r.david.murraylinkissue25619 messages
2015-11-13 19:41:26r.david.murraycreate