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 Jim.Jewett
Recipients Jim.Jewett, docs@python, georg.brandl, pitrou, python-dev, r.david.murray, sandro.tosi, vinay.sajip
Date 2012-04-09.19:26:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CA+OGgf5Cr+NOzpd=qkn9jJQG-=_Auo5WsngQNuAz3wPT2H-XQA@mail.gmail.com>
In-reply-to <1333997868.57.0.617708026995.issue14502@psf.upfronthosting.co.za>
Content
Vinay,

The current question is what contract locks should follow, and whether
all locks should follow it.  Would it be acceptable for
logging._releaseLock to raise a RuntimeError if the lock hadn't
previously been acquired?  In other words, would it be acceptable to
replace the current None with a counter (and to note in comments that
it should be safe from race conditions because it is only used when
threading isn't available).

-jJ
History
Date User Action Args
2012-04-09 19:26:27Jim.Jewettsetrecipients: + Jim.Jewett, georg.brandl, vinay.sajip, pitrou, r.david.murray, sandro.tosi, docs@python, python-dev
2012-04-09 19:26:26Jim.Jewettlinkissue14502 messages
2012-04-09 19:26:26Jim.Jewettcreate