Message 146615 - Python tracker

➜

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	loewis
Recipients	StevenY, loewis, martind, pitrou, skrah
Date	2011-10-29.17:41:30
SpamBayes Score	0.00025534313
Marked as misclassified	No
Message-id	<1319910091.36.0.258221221326.issue10363@psf.upfronthosting.co.za>
In-reply-to

Content
As a policy, we will not rely on C++ destructors for cleanup. There are really two issues here: "global" locks, and module-specific locks. The global locks can and should be released in Py_Finalize, with no API change. Antoine's patch looks good to me. For module-level locks, PEP-3121-style module finalization should be used. Patches are welcome. Martin: Please understand that there are MANY more issues with reloading Python in the same process, as a really large number of stuff doesn't get cleanup up on shutdown. Also expect that fixing these will take 10 years or more, unless somebody puts a huge effort into it.

As a policy, we will not rely on C++ destructors for cleanup. There are really two issues here: "global" locks, and module-specific locks.

The global locks can and should be released in Py_Finalize, with no API change. Antoine's patch looks good to me.

For module-level locks, PEP-3121-style module finalization should be used. Patches are welcome.

Martin: Please understand that there are *MANY* more issues with reloading Python in the same process, as a really large number of stuff doesn't get cleanup up on shutdown. Also expect that fixing these will take 10 years or more, unless somebody puts a huge effort into it.

History
Date	User	Action	Args
2011-10-29 17:41:31	loewis	set	recipients: + loewis, pitrou, skrah, martind, StevenY
2011-10-29 17:41:31	loewis	set	messageid: <1319910091.36.0.258221221326.issue10363@psf.upfronthosting.co.za>
2011-10-29 17:41:30	loewis	link	issue10363 messages
2011-10-29 17:41:30	loewis	create