[issue6721] Locks in python standard library should be sanitized on fork
Gregory P. Smith
report at bugs.python.org
Thu Feb 10 18:20:18 CET 2011
Gregory P. Smith <greg at krypto.org> added the comment:
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.
versions: +Python 3.3
Python tracker <report at bugs.python.org>
More information about the Python-bugs-list