logging and propagation
Vinay Sajip
vinay_sajip at yahoo.co.uk
Thu Nov 22 00:44:36 EST 2007
More information about the Python-list mailing list
Thu Nov 22 00:44:36 EST 2007
- Previous message (by thread): logging and propagation
- Next message (by thread): logging and propagation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Nov 21, 11:38 am, oj <ojee... at gmail.com> wrote: > Hi, > > I want to setuploggingwith two loggers: > > The child logger is used when something different needs to be done > with the log record, and the log record will propagate and be logged > by the root logger as usual. > > However, there are certain times when I don't want a log record to > propagate from the child to the parent. > > I don't really want to add a filter to the root logger, as it should > be up to the child whether the record propagates or not. > > I've tried setting the child to a lower level then the parent, but if > a record is dealt with by the child, the parent deals with it anyway > regardless of its own log level. > > Also, filters only apply particular handlers and do not affect > propagation. > > Can anyone suggest a simple way to achieve this? > > Currently, the only thing I can think of, is overriding the > callHandlers method in a custom Logger class. Do you already have a Logger subclass? Where and when is the decision being made about whether to propagate or not?
- Previous message (by thread): logging and propagation
- Next message (by thread): logging and propagation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list