[issue6721] Locks in python standard library should be sanitized on fork

[lesha]

lesha <pybug.20.lesha at xoxy.net> added the comment:

> So what are you suggesting?  That a lock of the default type should
> raise an error if you try to acquire it when it has been acquired in a 
> previous process?

I was suggesting a way to make 'logging' fork-safe. No more, no less.

Does what my previous comment make sense in light of this?

> Using a generation count

Sure, that's a good idea.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue6721>
_______________________________________