[issue6721] Locks in python standard library should be sanitized on fork
Antoine Pitrou
report at bugs.python.org
Mon Jan 23 22:58:32 CET 2012
Antoine Pitrou <pitrou at free.fr> added the comment:
> Is there any particular reason not to merge Charles-François's reinit_locks.diff?
>
> Reinitialising all locks to unlocked after a fork seems the only sane option.
I agree with this.
I haven't looked at the patch very closely. I think perhaps each lock
could have an optional callback for specific code to be run after
forking, but that may come in another patch.
(this would allow to make e.g. the C RLock fork-safe)
----------
_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue6721>
_______________________________________
More information about the Python-bugs-list
mailing list