On Dec 13, 5:03 pm, Andrea Crotti wrote:
> The set_verbosity seems to do its job, the second is also
> called and the filters are added but I don't see the output
> formatted as it should..
Generally speaking, you should only do logging configuration once, as
Jean-Michel said - from your main()
And by the way suppose I have a script which takes as input the log
level and a list of possible filters.
In another file I have a couple of functions as below which are called
in that order.
Is that supposed to work?
In theory I'm getting both times the same logger.
The set_verbosity seems to do
On 12/13/2011 04:11 PM, Jean-Michel Pichavant wrote:
Not really, if you use the classic way, your subloggers should be
created an never configured. Their default behavior is to raise any
log event to its parent. That way, all event logs end up being handled
by the root logger.
Ok thanks now
Andrea Crotti wrote:
I think is simple but I can't get it to work as I wish.
Suppose I have a big application, my idea is that the running
script sets a global logging level and then all the imported modules
would act consequently.
In my codebase, however, unless I set the level for each of the
I think is simple but I can't get it to work as I wish.
Suppose I have a big application, my idea is that the running
script sets a global logging level and then all the imported modules
would act consequently.
In my codebase, however, unless I set the level for each of the loggers
I don't get th
