This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ulrich.stern
Recipients docs@python, ulrich.stern
Date 2018-10-02.23:41:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1538523706.16.0.545547206417.issue34878@psf.upfronthosting.co.za>
In-reply-to
Content
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 locked."  The "not" should be deleted.  (Alternatively, one could change "locked" to "unlocked.")
History
Date User Action Args
2018-10-02 23:41:46ulrich.sternsetrecipients: + ulrich.stern, docs@python
2018-10-02 23:41:46ulrich.sternsetmessageid: <1538523706.16.0.545547206417.issue34878@psf.upfronthosting.co.za>
2018-10-02 23:41:46ulrich.sternlinkissue34878 messages
2018-10-02 23:41:46ulrich.sterncreate