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 pakal
Recipients eric.smith, pakal, vinay.sajip
Date 2010-04-07.08:05:45
SpamBayes Score 7.716662e-08
Marked as misclassified No
Message-id <1270627548.54.0.330947626887.issue8327@psf.upfronthosting.co.za>
In-reply-to
Content
Thanks for the doc patch, if you don't mind I'd just add the paragraph below too, to clarify the fact that logger levels are only "entry points" levels, ignored he rest of the time. There might be slight redundancies with the rest of the (long) documentation, but it's all benefit imo. B-)

"In addition to any handlers directly associated with a logger, *all handlers associated with all ancestors of the logger* are called to dispatch the message (unless the *propagate* flag for a logger is set to a false value, at which point the passing to ancestor handlers stops).

Note that in this process, the level of ancestor loggers is never considered : only their *propagate* attribute and the levels of their loggers canimpact the treatment on the message being dispatched. The level of a logger is thus only acting as an *entry point barrier*, only able to stop the whole dispatch of a message that enters the system through it."
History
Date User Action Args
2010-04-07 08:05:49pakalsetrecipients: + pakal, vinay.sajip, eric.smith
2010-04-07 08:05:48pakalsetmessageid: <1270627548.54.0.330947626887.issue8327@psf.upfronthosting.co.za>
2010-04-07 08:05:46pakallinkissue8327 messages
2010-04-07 08:05:46pakalcreate