ulrich.stern added the comment:
I still think the documentation should be changed, and an improved version
would look more like your comment than what it looks now. I assume to most
people "owning" means exclusively holding the lock, and a particular thread can
do this for Lock Objects.
Benjamin Peterson 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
New submission from ulrich.stern :
The first sentence of the documentation for Lock Objects
(https://docs.python.org/2/library/threading.html#lock-objects) seems
incorrect. It currently states "A primitive lock is a synchronization
primitive that is not owned by a particular thread when
