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
Date 2009-07-02.09:50:29
SpamBayes Score 0.0006752689
Marked as misclassified No
Message-id <1246528231.33.0.0905986098741.issue6399@psf.upfronthosting.co.za>
In-reply-to
Content
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 :-\ to realise I had misspelt "propagate".

Wouldn't it be better if spurious names raised parsing exceptions?

Thanks,
Mike.

P.S. Another thing that might have helped me track this down a little
quicker is if I could have printed the name of the logger that was the
source of some output. %(name)s gives the logger that *received* the log
message.  If there was another format variable for the logger that was
the source of a log message I would have seen one message from Builder
and one message from root and it would have been more obvious what was
going on.
History
Date User Action Args
2009-07-02 09:50:31mikesetrecipients: + mike
2009-07-02 09:50:31mikesetmessageid: <1246528231.33.0.0905986098741.issue6399@psf.upfronthosting.co.za>
2009-07-02 09:50:30mikelinkissue6399 messages
2009-07-02 09:50:29mikecreate