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 ajs, chris.jerdonek, docs@python, r.david.murray, vinay.sajip
Date 2013-01-29.19:33:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1359488037.16.0.414873633339.issue17075@psf.upfronthosting.co.za>
In-reply-to
Content
Indeed.  The whole point of that section is to explain how the library can refrain from spewing unwanted logging *if the application doesn't care about logging*.  If the application does care (has configured logging), it would be wrong to block the logging.

I believe there is now a NullHandler or something similar set up by default, so I don't think this issue arises in Python3.
History
Date User Action Args
2013-01-29 19:33:57r.david.murraysetrecipients: + r.david.murray, vinay.sajip, ajs, chris.jerdonek, docs@python
2013-01-29 19:33:57r.david.murraysetmessageid: <1359488037.16.0.414873633339.issue17075@psf.upfronthosting.co.za>
2013-01-29 19:33:57r.david.murraylinkissue17075 messages
2013-01-29 19:33:57r.david.murraycreate