Mike pyt...@amadron.com added the comment:
Hi Vinay,
I will bow to your greater expertise on this and will let this go.
It looks like it will be far more easier and robust just to invent my
own logging config file format and read it myself.
Thanks for your help.
Mike.
--
status: open -
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
Mike,
That's just fine. Sorry if I appear unhelpful, but in the open source
world we mostly scratch our own itches. I believe I have a reasonable
record on accepting patches from the community (though I don't of course
accept everything),
Mike pyt...@amadron.com added the comment:
Sorry, I only started learning Python a couple of weeks ago. Didn't
know that there was a ConfigParser module. So this would really be a
feature request of ConfigParser?
Interesting you should mention Postel's Law. Being liberal about what
you
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
Well, there are other systems around (e.g. ConfigObj) which will allow
you to validate against a schema, but it's not part of the core so
logging can't rely on it.
I'm not sure how much interest there'd be in adding this kind of
validation
Mike pyt...@amadron.com added the comment:
Fair point. Agree that this is a feature request. Perhaps something like:
logging.config.fileConfig(path, strict=False)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6399
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment:
I'm not sure that this is a valid feature request. As R. David Murray
has said, it's sort of an unwritten rule of ConfigParser-based
applications that they look for specific entries, but don't care what
else is there in the file - sort of in
New submission from Mike pyt...@amadron.com:
Hi,
I had a logging.conf file with the following logger def in it:
[logger_Builder]
level=DEBUG
handlers=consoleStderr
qualname=Builder
propogate=0
And I couldn't understand why all my log messages were coming out twice.
It took me four hours :-\
R. David Murray rdmur...@bitdance.com added the comment:
Ignoring unknown options in the configuration file is analogous to
ignoring unknown tags in html: it makes it easier to use the same config
file with multiple versions of the logger, with older versions ignoring
the options they don't
