➜

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 r.david.murray
Recipients Jim.Jewett, docs@python, georg.brandl, pitrou, python-dev, r.david.murray, sandro.tosi
Date 2012-04-06.19:43:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333741427.67.0.875101874385.issue14502@psf.upfronthosting.co.za>
In-reply-to
Content 
It doesn't matter *how* you get to the situation where you are releasing a lock that hasn't been acquired, the point is to document what actually happens when you do the release.  And just yesterday I needed to know this, since I have a lock that may or may not be currently held when I release it, and now I know I can just catch RuntimeError in that case.
History
Date User Action Args
2012-04-06 19:43:47r.david.murraysetrecipients: + r.david.murray, georg.brandl, pitrou, sandro.tosi, docs@python, python-dev, Jim.Jewett
2012-04-06 19:43:47r.david.murraysetmessageid: <1333741427.67.0.875101874385.issue14502@psf.upfronthosting.co.za>
2012-04-06 19:43:47r.david.murraylinkissue14502 messages
2012-04-06 19:43:47r.david.murraycreate