This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author mike
Recipients mike, r.david.murray, vinay.sajip
Date 2009-07-07.11:20:16
SpamBayes Score 9.844985e-06
Marked as misclassified No
Message-id <1246965618.66.0.230223554595.issue6399@psf.upfronthosting.co.za>
In-reply-to
Content
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 accept from others doesn't mean ignoring non-conformance.  Jon
Postel was clear that although you endeavour to continue when
encountering non-conformance you should always report it, lest
non-conformance propogates (sic).

I can think of two ways ConfigParser could report these problems. 
Either you give it a callback function it can call as it encounters
problems, or, after you have parsed a file you can call another function
that gives a list of any problems encountered.

If ConfigParser had this functionality it would then be straightforward
for the logging.config.fileConfig module to send these warnings to the
root logger.
History
Date User Action Args
2009-07-07 11:20:18mikesetrecipients: + mike, vinay.sajip, r.david.murray
2009-07-07 11:20:18mikesetmessageid: <1246965618.66.0.230223554595.issue6399@psf.upfronthosting.co.za>
2009-07-07 11:20:17mikelinkissue6399 messages
2009-07-07 11:20:16mikecreate