By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,199 Members | 1,064 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,199 IT Pros & Developers. It's quick & easy.

Multiple calls to logging.config.fileConfig

P: n/a

our applications can have plugins as subpackages and I'd like to allow
them to use their own logger as well as it's configuration. I thought
that best way will be their own configuration file passed to

However, I run into problems...

1) It seems that I cannot refer to something from previously loaded
files, i.e. I'd like application config file to specify formatters and
handlers and plugins only referring them.

2) I'm not sure about "appending" loggers; if I specify
keys: web

and then
keys: syncml

Will web not be overwritten?

3) Finally, I run into "root" problem. In second call, if I specify
root logger again:

keys: root,web


level: WARNING
qualname: xxx.web
handlers: console

I'll get

Traceback (most recent call last):
File "/usr/lib/python2.4/logging/", line 143, in fileConfig
If I'll set only web as logger, I'll get standard NoSectionFound

Any idea how to fix this? It seems that I have to write custom parser
merging all files and config logging directly from code, but I'd like
to assure that it's the standard way...



Oct 5 '06 #1
Share this Question
Share on Google+
1 Reply

P: n/a
logging.config.fileConfig() does not do incremental configuration - it
replaces the existing configuration with the configuration in the file
passed to fileConfig. While this might not be too useful for your
current needs, the present behaviour is by design...fileConfig is meant
to choose between one of a number of configurations (e.g. development,
test, production) and not for incremental configuration.


Vinay Sajip

Oct 7 '06 #2

This discussion thread is closed

Replies have been disabled for this discussion.