Hello Vinay,
On Sun, Jun 04, 2006 at 05:23:55AM -0700, Vinay Sajip wrote:
> It's not propagated to the root logger (or to ancestor loggers in
> general) - just to the handlers associated with ancestor loggers.
...
> You can set levels on handlers as well as loggers. So if you add a
> syslog handle
Hello Vinay,
On Wed, May 31, 2006 at 03:05:13PM -0700, Vinay Sajip wrote:
> > Hmm, log1 decides once whether to print an event, and after that it gets
> > printed in log1 and all its ancestors, regardless of their level? I find
> > this quite counter-intuitive. I'd instead expect that each logger
Hello Vinay,
On Thu, May 25, 2006 at 10:14:00AM -0700, Vinay Sajip wrote:
> I don't know what your logger hierarchy looks like: you could perhaps
> log to child loggers of l01 ("l01.XXX"), or set all other loggers you
> use to have a CRITICAL level, or filter them using a filter which
> filters ou
Hello Vinay,
On Tue, May 23, 2006 at 04:13:38PM -0700, Vinay Sajip wrote:
> > [logger_root]
> > level=CRITICAL
> > handlers=console
> >
> > [logger_l01]
> > level=DEBUG
> > qualname=l01
> > handlers=console
> >
> > I want logger_root to go to /dev/null, so I've configured it with level
> > CRITIC
Hello all,
I want that each module has its own logger. I've defined the following
config file:
[formatters]
keys=f01
[handlers]
keys=console
[loggers]
keys=root,l01
[formatter_f01]
format=%(name)s: %(message)s
[handler_console]
class=StreamHandler
args=[]
formatter=f01
[logger_root]
level=CR
