Author vinay.sajip
Recipients mike, r.david.murray, vinay.sajip
Date 2009-07-03.17:05:06
SpamBayes Score 2.30249e-08
Marked as misclassified No
Message-id <>
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 line with Postel's Law.

The appearance of multiple messages pretty much points to multiple
handlers handling the message; knowing the way the hierarchy works,
propagation should have been one of the first things to check (as I
assume you had added handlers both at and above [logger_Builder]. I know
hindsight is wonderful, and I'm sorry it took you 4 hours to find the
problem; but I'm not convinced by this that I need to put more error
checking into the fileConfig code.
Date User Action Args
2009-07-03 17:05:08vinay.sajipsetrecipients: + vinay.sajip, r.david.murray, mike
2009-07-03 17:05:08vinay.sajipsetmessageid: <>
2009-07-03 17:05:06vinay.sajiplinkissue6399 messages
2009-07-03 17:05:06vinay.sajipcreate