On Wed, Sep 29, 2010 at 10:30:40AM +0200, Fabrice Estiévenart wrote: > Thank you Marius for your suggestion, > > After a short investigation, I notice that, for a strange reason, the > script is searching for a section named [logger_ routes] (with a blank > space between _ and routes) while my .ini file has a [logger_routes] > section (without the blank space).
Yes, yes.
There's a [loggers] section with keys = foo, bar, .... The logging
framework takes each of those and looks for [logger_foo], [logger_bar],
....
You either have a weird keys list that causes that space to become part
of the logger name, or a buggy version of logging (which is in the
standard library and shouldn't be buggy -- do you have a different
version in your sys.path perhaps?).
> Other problem related to logging: the script does not find the key
> 'threadName' in the logger format.
> format = %(asctime)s %(levelname)-5.5s [%(name)s] [%(threadName)s] %(message)s
>
> Is it a bug in the logging package ? Wrong versions or dependencies ?
> Do you have some suggestions ?
I think you have an outdated copy of logging somewhere in your python
path. threadName's been in the stdlib's logging since forever
(according to the documentation, and a quick check of Python 2.4 through
2.6 sources).
Marius Gedminas
--
I am Lalo of deB-org. You will be freed. Resistance is futile.
-- from the sig of Lalo Martins
signature.asc
Description: Digital signature
