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 bquinlan, brian.curtin, georg.brandl, lukasz.langa, ncoghlan, pitrou, r.david.murray
Date 2010-12-06.22:23:45
SpamBayes Score 0.0001521772
Marked as misclassified No
Message-id <1291674229.05.0.784264888971.issue10626@psf.upfronthosting.co.za>
In-reply-to
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, but I just tested it and you are right, it complains about not having a handler.  

This definitely seems like a logging bug to me.  IMO the only thing a module should need to do is call getlogger with its qualified name and log messages.
History
Date User Action Args
2010-12-06 22:23:49r.david.murraysetrecipients: + r.david.murray, georg.brandl, bquinlan, ncoghlan, pitrou, brian.curtin, lukasz.langa
2010-12-06 22:23:49r.david.murraysetmessageid: <1291674229.05.0.784264888971.issue10626@psf.upfronthosting.co.za>
2010-12-06 22:23:45r.david.murraylinkissue10626 messages
2010-12-06 22:23:45r.david.murraycreate