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 Johz, docs@python, vinay.sajip
Date 2013-09-05.15:01:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378393294.26.0.903851038693.issue18933@psf.upfronthosting.co.za>
In-reply-to
Content
Why for the logging module in particular? This isn't the norm for stdlib packages, AFAIK.

The logging documentation (both tutorial and reference) is supposed to stand on its own, and in general I don't expect documentation users to (have to) look at the source to understand how to use logging.

If you think particular aspects of the documentation need clarifying, then please indicate what they are and suggest what sort of improvements you think are in order.
History
Date User Action Args
2013-09-05 15:01:34vinay.sajipsetrecipients: + vinay.sajip, docs@python, Johz
2013-09-05 15:01:34vinay.sajipsetmessageid: <1378393294.26.0.903851038693.issue18933@psf.upfronthosting.co.za>
2013-09-05 15:01:34vinay.sajiplinkissue18933 messages
2013-09-05 15:01:34vinay.sajipcreate