From: Vinay Sajip Date: Mon, 20 Feb 2012 18:35:26 +0000 (+0000) Subject: logging: clarified documentation for Handler.handleError. X-Git-Tag: v3.2.3rc1~35 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fee358b0df547e9451cfb0b3d25980e6cc7177cc;p=thirdparty%2FPython%2Fcpython.git logging: clarified documentation for Handler.handleError. --- diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst index 5a4116053a27..c429c85985be 100644 --- a/Doc/library/logging.rst +++ b/Doc/library/logging.rst @@ -375,12 +375,14 @@ subclasses. However, the :meth:`__init__` method in subclasses needs to call .. method:: Handler.handleError(record) This method should be called from handlers when an exception is encountered - during an :meth:`emit` call. By default it does nothing, which means that - exceptions get silently ignored. This is what is mostly wanted for a logging - system - most users will not care about errors in the logging system, they are - more interested in application errors. You could, however, replace this with a - custom handler if you wish. The specified record is the one which was being - processed when the exception occurred. + during an :meth:`emit` call. If the module-level attribute + ``raiseExceptions`` is ``False``, exceptions get silently ignored. This is + what is mostly wanted for a logging system - most users will not care about + errors in the logging system, they are more interested in application + errors. You could, however, replace this with a custom handler if you wish. + The specified record is the one which was being processed when the exception + occurred. (The default value of ``raiseExceptions`` is ``True``, as that is + more useful during development). .. method:: Handler.format(record)