From: Vinay Sajip Date: Mon, 21 Jan 2013 21:56:35 +0000 (+0000) Subject: Issue #17007: Made minor changes to documentation wording. X-Git-Tag: v2.7.4rc1~164^2~53 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=8a459d977db10cb1bf8ef967b2b5fb412d54a6f3;p=python Issue #17007: Made minor changes to documentation wording. --- diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst index 27736440ee..524a7e8214 100644 --- a/Doc/library/logging.rst +++ b/Doc/library/logging.rst @@ -83,14 +83,14 @@ is the module's name in the Python package namespace. The constructor sets this attribute to ``True``. - .. note:: If you attach a handler to several loggers, it may emit the same - record multiple times. In general, you should not need to attach a - handler to more than one logger - if you just attach it to the - appropriate logger which is highest in the logger hierarchy, then it - will see all events logged by all descendant loggers, provided that - their propagate setting is left set to ``True``. A common scenario is to - attach handlers only to the root logger, and let propagation take care of - the rest. + .. note:: If you attach a handler to a logger *and* one or more of its + ancestors, it may emit the same record multiple times. In general, you + should not need to attach a handler to more than one logger - if you just + attach it to the appropriate logger which is highest in the logger + hierarchy, then it will see all events logged by all descendant loggers, + provided that their propagate setting is left set to ``True``. A common + scenario is to attach handlers only to the root logger, and to let + propagation take care of the rest. .. method:: Logger.setLevel(lvl)