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 lesha
Recipients lesha
Date 2012-01-13.09:33:03
SpamBayes Score 2.3358516e-05
Marked as misclassified No
Message-id <1326447184.81.0.483004190361.issue13778@psf.upfronthosting.co.za>
In-reply-to
Content
Actually, I think it does not matter which thread owns the lock, it is still invalid to try to acquire a lock that was grabbed by the fork() parent. Why? Because the fork() parent cannot free the child's copy of the lock anyway, and it's guaranteed to be dead also.
History
Date User Action Args
2012-01-13 09:33:04leshasetrecipients: + lesha
2012-01-13 09:33:04leshasetmessageid: <1326447184.81.0.483004190361.issue13778@psf.upfronthosting.co.za>
2012-01-13 09:33:04leshalinkissue13778 messages
2012-01-13 09:33:04leshacreate