Author vinay.sajip
Recipients bquinlan, brian.curtin, georg.brandl, lukasz.langa, ncoghlan, pitrou, r.david.murray, vinay.sajip
Date 2010-12-07.11:40:22
SpamBayes Score 3.76154e-05
Marked as misclassified No
Message-id <1291722024.26.0.676718139621.issue10626@psf.upfronthosting.co.za>
In-reply-to
Content
I will take a look at test_logging tidying up after itself, though the intention is to leave things as they were found (this is done in setUp/tearDown, and if it doesn't tidy up properly, that would be a bug).

As already explained in logging's documentation, there is no problem with just getting a logger and logging to it, BUT the top-level logger in any library package (and that includes stdlib, too) should have a NullHandler instance added to avoid the "no handlers could be found for logger XXX" message. This latter, one-off message is only there to guard against mis-configuration.

Re. Nick's comments about using logging in the stdlib - I'm not sure the reason he states is the reason for lack of traction, I think it's more to do with inertia. I will post separately on python-dev about use of logging in the stdlib itself, to see what specific obstacles stdlib maintainers see in the use of logging in their own modules.
History
Date User Action Args
2010-12-07 11:40:24vinay.sajipsetrecipients: + vinay.sajip, georg.brandl, bquinlan, ncoghlan, pitrou, r.david.murray, brian.curtin, lukasz.langa
2010-12-07 11:40:24vinay.sajipsetmessageid: <1291722024.26.0.676718139621.issue10626@psf.upfronthosting.co.za>
2010-12-07 11:40:22vinay.sajiplinkissue10626 messages
2010-12-07 11:40:22vinay.sajipcreate