Author collinwinter
Recipients
Date 2007-03-15.20:38:48
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to
Content
Isn't that (unavailable resources) a problem with atexit handlers in general, regardless of where they occur in Py_Finalize()? All existing low-level exitfuncs are already guaranteed not to mess with interpreter/thread state, simply because they can't (as things stand). If exitfuncs written against 3.0+ start messing around with Python's internal state, that's a bug in the exitfunc. We're all adults, etc.

I'm attaching the new version of my patch, which includes atexit.unregister().
File Added: atexit.patch
History
Date User Action Args
2007-08-23 15:57:33adminlinkissue1680961 messages
2007-08-23 15:57:33admincreate