[Python-checkins] cpython (2.7): logging: clarified documentation for Handler.handleError.

Mon Feb 20 19:51:09 CET 2012

http://hg.python.org/cpython/rev/37494e44265c
changeset: 75061:37494e44265c
branch: 2.7
parent: 75053:7ff4731853e2
user: Vinay Sajip <vinay_sajip at yahoo.co.uk>
date: Mon Feb 20 18:34:07 2012 +0000
summary:
 logging: clarified documentation for Handler.handleError.
files:
 Doc/library/logging.rst | 14 ++++++++------
 1 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst
--- a/Doc/library/logging.rst
+++ b/Doc/library/logging.rst
@@ -339,12 +339,14 @@
 .. 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)
-- 
Repository URL: http://hg.python.org/cpython
