Message151267
| Author |
gregory.p.smith |
| Recipients |
Giovanni.Bajo, avian, bobbyi, gregory.p.smith, jcea, lesha, neologix, nirai, pitrou, sbt, sdaoden, vstinner |
| Date |
2012年01月14日.19:40:51 |
| SpamBayes Score |
3.865887e-10 |
| Marked as misclassified |
No |
| Message-id |
<1326570052.5.0.861056478517.issue6721@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
A new lock type will NOT solve this. It is ALWAYS okay to clear all thread/threading module locks after a fork.
They are and always have been process-local by definition so they are also by definition 100% invalid to any child process.
Anyone who has written code using them to "lock" an out-of-process resource has written code that is already broken today. Thread locks can't guard network resources. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2012年01月14日 19:40:52 | gregory.p.smith | set | recipients:
+ gregory.p.smith, jcea, pitrou, vstinner, nirai, bobbyi, neologix, Giovanni.Bajo, sdaoden, sbt, avian, lesha |
| 2012年01月14日 19:40:52 | gregory.p.smith | set | messageid: <1326570052.5.0.861056478517.issue6721@psf.upfronthosting.co.za> |
| 2012年01月14日 19:40:51 | gregory.p.smith | link | issue6721 messages |
| 2012年01月14日 19:40:51 | gregory.p.smith | create |
|