[Python-checkins] cpython (3.2): Issue #17007: Made minor changes to documentation wording.

[vinay.sajip]

http://hg.python.org/cpython/rev/c8614ec54a63
changeset:   81642:c8614ec54a63
branch:      3.2
parent:      81638:029785354dbc
user:        Vinay Sajip <vinay_sajip at yahoo.co.uk>
date:        Mon Jan 21 21:57:10 2013 +0000
summary:
  Issue #17007: Made minor changes to documentation wording.

files:
  Doc/library/logging.rst |  16 ++++++++--------
  1 files changed, 8 insertions(+), 8 deletions(-)


diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst
--- a/Doc/library/logging.rst
+++ b/Doc/library/logging.rst
@@ -81,14 +81,14 @@
 
    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)
 

-- 
Repository URL: http://hg.python.org/cpython