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 doughellmann, eric.smith, georg.brandl, michael.foord, ncoghlan, pitrou, r.david.murray, theller, vinay.sajip
Date 2009-09-21.20:58:34
SpamBayes Score 0.000402084
Marked as misclassified No
Message-id <1253566715.64.0.253946245132.issue6958@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think this is about logging in stdlib modules that are run
directly. I think this is about a library that contains logging calls
(eg: multiprocessing), and is used in j-random-application, and while
prototyping/debugging the application you want to access that logging
information without having to write a logging infrastructure into your
app first.  Or you want to access it while debugging someone _else_'s
application...
History
Date User Action Args
2009-09-21 20:58:35r.david.murraysetrecipients: + r.david.murray, theller, georg.brandl, vinay.sajip, ncoghlan, pitrou, eric.smith, doughellmann, michael.foord
2009-09-21 20:58:35r.david.murraysetmessageid: <1253566715.64.0.253946245132.issue6958@psf.upfronthosting.co.za>
2009-09-21 20:58:34r.david.murraylinkissue6958 messages
2009-09-21 20:58:34r.david.murraycreate