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 pitrou
Recipients Jim.Jewett, docs@python, georg.brandl, pitrou, python-dev, sandro.tosi
Date 2012-04-05.21:38:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333661578.3326.12.camel@localhost.localdomain>
In-reply-to <1333661714.57.0.492844768267.issue14502@psf.upfronthosting.co.za>
Content
> At least put the information inside some disclaimers about "normally";
> even the stdlib has some fake locks that let you release a lock
> someone else holds.

Not sure what you're talking about. The doc patch is about unacquired
locks, not locks that someone else (another thread) holds.

Indeed the standard Lock object (but not the RLock) does allow releasing
from another thread. It's a feature (which makes it serve as a binary
semaphore).
History
Date User Action Args
2012-04-05 21:38:18pitrousetrecipients: + pitrou, georg.brandl, sandro.tosi, docs@python, python-dev, Jim.Jewett
2012-04-05 21:38:17pitroulinkissue14502 messages
2012-04-05 21:38:17pitroucreate