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-06.09:57:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333705934.3395.0.camel@localhost.localdomain>
In-reply-to <CA+OGgf7OYFVhEAznD4xZKJwg1WKxo7KWNXAtmKSvpPjSJFs5Bw@mail.gmail.com>
Content
> On Thu, Apr 5, 2012 at 5:38 PM, Antoine Pitrou <report@bugs.python.org> wrote:
> > Antoine Pitrou <pitrou@free.fr> added the comment:
> 
> > Not sure what you're talking about. The doc patch is about unacquired
> > locks, not locks that someone else (another thread) holds.
> 
> Isn't one common reason for not being able to acquire a lock that
> someone else was already holding it?

We're talking about *releasing* an (un)acquired lock, not acquiring it
again...
History
Date User Action Args
2012-04-06 09:57:33pitrousetrecipients: + pitrou, georg.brandl, sandro.tosi, docs@python, python-dev, Jim.Jewett
2012-04-06 09:57:33pitroulinkissue14502 messages
2012-04-06 09:57:33pitroucreate