Benjamin Peterson <benja...@python.org> added the comment:
The current documentation is correct. While conceptually one may think of a
lock as being held ("owned") by a particular thread, the lock internally has no
idea what thread owns it—operations on a lock are influenced only by its
current state not what thread is performing the operation. It's perfectly
possible, if inadvisable, to release a lock on a thread different from the one
it was acquired on. The description of ownership is meant to draw a distinction
with recursive locks, which do have an internal notion of ownership.
----------
nosy: +benjamin.peterson
resolution: -> not a bug
stage: -> resolved
status: open -> closed
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue34878>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
