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 bradallen
Recipients bradallen
Date 2008-03-19.16:55:26
SpamBayes Score 0.034276
Marked as misclassified No
Message-id <>
The logging module contains several bare except statements. It's
understandable that the logging module should be completely silent, but
in the case of logging.config, the bare except can make it very
difficult to identify when there is a problem with a customer handler or
even with configuration.

These are the offending lines (lines 133-134): 

except: #if an error occurs when instantiating a handler, too bad
    pass    #this could happen e.g. because of lack of privileges

Maybe this should only catch OSError, so that other problems will
generate a failure at this point and show the correct traceback. My
experience is that there is usually a failure anyway when there is a
configuration problem, but the error is usually misleading.

By the way, exceptions generated here seem to mainly occur when a Python
script is first starting up, as it involves the initial configuration. I
am not convinced that the logging module should be silent at that stage.
Date User Action Args
2008-03-19 16:55:28bradallensetspambayes_score: 0.034276 -> 0.034276
recipients: + bradallen
2008-03-19 16:55:27bradallensetspambayes_score: 0.034276 -> 0.034276
messageid: <>
2008-03-19 16:55:27bradallenlinkissue2424 messages
2008-03-19 16:55:26bradallencreate