[issue21342] multiprocessing RLock and Lock raise incorrect exceptions when releasing an unlocked lock.

[Davin Potts]

Davin Potts added the comment:

The discussion in issue23484 is leading to a recommendation that the docs be changed to reflect the actual behavior of multiprocessing's Lock and its close relatives.

As far back as 2.6.9, calling release() on an unlocked threading.Lock triggered a thread.error Exception whereas doing the same on multiprocessing.Lock triggered a ValueError.  This discrepancy in the behavior of Lock between modules turns out to not be a recent development.

If issue23484 moves forward with changing the documentation to reflect reality, this issue would be addressed as well.

----------
dependencies: +SemLock acquire() keyword arg 'blocking' is invalid
nosy: +davin

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