Message139489
| 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. |
|