➜

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 nirai
Recipients Giovanni.Bajo, avian, bobbyi, gregory.p.smith, neologix, nirai, pitrou, sdaoden, vstinner
Date 2011-06-30.15:10:11
SpamBayes Score 5.2923773e-05
Marked as misclassified No
Message-id <1309446611.99.0.528307762992.issue6721@psf.upfronthosting.co.za>
In-reply-to
Content 
> I believe that the comp.programming.threads post from > David Butenhof linked above explains why adding atfork() > handlers isn't going to solve this. In Python atfork() handlers will never run from signal handlers, and if I understood correctly, Charles-François described a way to "re-initialize" a Python lock safely under that assumption.
History
Date User Action Args
2011-06-30 15:10:12niraisetrecipients: + nirai, gregory.p.smith, pitrou, vstinner, bobbyi, neologix, Giovanni.Bajo, sdaoden, avian
2011-06-30 15:10:11niraisetmessageid: <1309446611.99.0.528307762992.issue6721@psf.upfronthosting.co.za>
2011-06-30 15:10:11nirailinkissue6721 messages
2011-06-30 15:10:11niraicreate