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 sbt
Recipients Arfrever, chortos, pitrou, sbt, serhiy.storchaka, terry.reedy
Date 2013-09-25.16:06:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1380125198.77.0.555613148128.issue19021@psf.upfronthosting.co.za>
In-reply-to
Content
The clearing of modules at shutdown has been substantially changed in 3.4.  Now a best effort is made to let the module go away purely by gc.  Those modules which survive get purged in random order.

In 3.3 all modules were purged, but builtins was special cased to be purged last.  (See Python/import.c:PyImport_Cleanup().)

I would favour setting a flag before the purging stage which prevents __del__ methods (and weakrefs?) from running.
History
Date User Action Args
2013-09-25 16:06:38sbtsetrecipients: + sbt, terry.reedy, pitrou, Arfrever, chortos, serhiy.storchaka
2013-09-25 16:06:38sbtsetmessageid: <1380125198.77.0.555613148128.issue19021@psf.upfronthosting.co.za>
2013-09-25 16:06:38sbtlinkissue19021 messages
2013-09-25 16:06:38sbtcreate