Message128316
Yeah, I'm trying to figure out what I was thinking then or if I was just plain wrong. :)
I was clearly wrong about a release being done in the child being the right thing to do (issue6643 proved that, the state held by a lock is not usable to another process on all platforms such that release even works).
Part of it looks like I wanted a way to detect it was happening as any lock that is held during a fork indicates a _potential_ bug (the lock wasn't registered anywhere to be released before the fork) but not everything needs to care about that. |
|
Date |
User |
Action |
Args |
2011-02-10 17:20:18 | gregory.p.smith | set | recipients:
+ gregory.p.smith, pitrou, bobbyi, neologix |
2011-02-10 17:20:18 | gregory.p.smith | set | messageid: <1297358418.19.0.0185346544457.issue6721@psf.upfronthosting.co.za> |
2011-02-10 17:20:17 | gregory.p.smith | link | issue6721 messages |
2011-02-10 17:20:17 | gregory.p.smith | create | |
|