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 grahamd
Recipients grahamd, neologix, pitrou, tarek
Date 2012-02-22.09:34:59
SpamBayes Score 1.8848408e-07
Marked as misclassified No
Message-id <1329903300.83.0.553554542217.issue14073@psf.upfronthosting.co.za>
In-reply-to
Content
I haven't said I am against it. All I have done so far is explain on the WEB-SIG how mod_wsgi works and how Python currently works and how one would normally handle this situation by having the thread be daemonised.

As for the proposed solution, where is the code example showing how what you are suggesting is meant to work. Right now you are making people assume how that would work. Add an actual example here at least of how with the proposed feature your code would then look.

For the benefit of those who might even implement what you want, which will not be me anyway as I am not involved in Python core development, you might also explain where you expect these special per thread atexit callbacks to be triggered within the current steps for shutting down the interpreter. That way it will be more obvious to those who come later as to what you are actually proposing.
History
Date User Action Args
2012-02-22 09:35:00grahamdsetrecipients: + grahamd, pitrou, tarek, neologix
2012-02-22 09:35:00grahamdsetmessageid: <1329903300.83.0.553554542217.issue14073@psf.upfronthosting.co.za>
2012-02-22 09:35:00grahamdlinkissue14073 messages
2012-02-22 09:34:59grahamdcreate