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 pitrou
Recipients bquinlan, brian.curtin, georg.brandl, lukasz.langa, ncoghlan, pitrou, r.david.murray
Date 2010-12-06.22:30:26
SpamBayes Score 0.00015272
Marked as misclassified No
Message-id <1291674623.3579.7.camel@localhost.localdomain>
In-reply-to <1291674229.05.0.784264888971.issue10626@psf.upfronthosting.co.za>
Content
> Wow, I didn't realize that's how logging worked.  My understanding was
> a module should just get a logger and log messages, and if the
> application didn't do any setup beforehand, the first logging call
> would cause messages to be written to stdout (or stderr) in a default
> format.  In fact, I thought that I had observed that behavior in the
> past,

So have I. Did something change?

And does test_logging really have to change the whole logging setup,
rather than only what it needs to check for? Or can't it restore stuff
afterwards?
History
Date User Action Args
2010-12-06 22:30:28pitrousetrecipients: + pitrou, georg.brandl, bquinlan, ncoghlan, r.david.murray, brian.curtin, lukasz.langa
2010-12-06 22:30:26pitroulinkissue10626 messages
2010-12-06 22:30:26pitroucreate