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 vstinner
Recipients brett.cannon, pitrou, python-dev, vstinner
Date 2013-10-28.18:43:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1382985834.64.0.25564317271.issue19421@psf.upfronthosting.co.za>
In-reply-to
Content
"Again, I don't think this is a good patch. If you want to disable module imports during shutdown, it should be done inside the import machinery, 
not duplicated at every call site."

Ah sorry, I misunderstood your previous comment. I agree that  traceback_finalize.patch is very specific.

Here is a new patch "import_finalization.patch", which block importing new modules (and import again unloaded modules) during finalization.

The full test suite pass with the patch, so at least no unit test tries to import a module during finalization.

> (but I don't necessarily agree that it's a good idea, either)

I'm opening a thread on python-dev to discuss this tricky question.
History
Date User Action Args
2013-10-28 18:43:54vstinnersetrecipients: + vstinner, brett.cannon, pitrou, python-dev
2013-10-28 18:43:54vstinnersetmessageid: <1382985834.64.0.25564317271.issue19421@psf.upfronthosting.co.za>
2013-10-28 18:43:54vstinnerlinkissue19421 messages
2013-10-28 18:43:54vstinnercreate