From: Vinay Sajip Date: Thu, 19 Aug 2010 19:17:41 +0000 (+0000) Subject: Issue #9606: Updated documentation for Filter objects. X-Git-Tag: v2.7.1rc1~385 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=3478ac066b1d5367b5f818df7aa65a1a16912755;p=python Issue #9606: Updated documentation for Filter objects. --- diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst index b2f98d0373..f257643b72 100644 --- a/Doc/library/logging.rst +++ b/Doc/library/logging.rst @@ -2558,6 +2558,13 @@ initialized with the empty string, all events are passed. yes. If deemed appropriate, the record may be modified in-place by this method. +Note that filters attached to handlers are consulted whenever an event is +emitted by the handler, whereas filters attached to loggers are consulted +whenever an event is logged to the handler (using :meth:`debug`, :meth:`info`, +etc.) This means that events which have been generated by descendant loggers +will not be filtered by a logger's filter setting, unless the filter has also +been applied to those descendant loggers. + .. _log-record: LogRecord Objects