➜

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.

作者 gregory.p.smith
收信人 Giovanni.Bajo, avian, bobbyi, gregory.p.smith, jcea, lesha, neologix, nirai, pitrou, sbt, sdaoden, vstinner
日期 2012-01-14.19:40:51
SpamBayes Score 3.865887e-10
Marked as misclassified 否
Message-id <1326570052.5.0.861056478517.issue6721@psf.upfronthosting.co.za>
In-reply-to
内容 
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.
历史
日期 用户 动作 参数
2012-01-14 19:40:52gregory.p.smith修改recipients: + gregory.p.smith, jcea, pitrou, vstinner, nirai, bobbyi, neologix, Giovanni.Bajo, sdaoden, sbt, avian, lesha
2012-01-14 19:40:52gregory.p.smith修改messageid: <1326570052.5.0.861056478517.issue6721@psf.upfronthosting.co.za>
2012-01-14 19:40:51gregory.p.smith链接issue6721 messages
2012-01-14 19:40:51gregory.p.smith创建