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 vinay.sajip
Recipients Jim.Jewett, docs@python, georg.brandl, pitrou, python-dev, r.david.murray, sandro.tosi, vinay.sajip
Date 2012-04-09.18:57:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1333997868.57.0.617708026995.issue14502@psf.upfronthosting.co.za>
In-reply-to
Content
Re. logging, logging._acquireLock and logging._releaseLock are not part of the public API and are undocumented at present. The case when _releaseLock does not raise an error is when threading couldn't be imported, so the _lock variable is None. I don't see the need for adding any documentation for this.

Logging doesn't use dummy_thread: if threading isn't available, all lock acquisition and release operations become no-ops.
History
Date User Action Args
2012-04-09 18:57:48vinay.sajipsetrecipients: + vinay.sajip, georg.brandl, pitrou, r.david.murray, sandro.tosi, docs@python, python-dev, Jim.Jewett
2012-04-09 18:57:48vinay.sajipsetmessageid: <1333997868.57.0.617708026995.issue14502@psf.upfronthosting.co.za>
2012-04-09 18:57:48vinay.sajiplinkissue14502 messages
2012-04-09 18:57:47vinay.sajipcreate