From: Vinay Sajip <vinay_sajip@yahoo.co.uk>
Date: Fri, 30 Sep 2005 12:08:25 +0000 (+0000)
Subject: Minor clarification of effective level calculation
X-Git-Tag: v2.4.3c1~262
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=33c249475c7fb1a9608ee44d0b76cf0786b7fb9f;p=thirdparty%2FPython%2Fcpython.git

Minor clarification of effective level calculation
---

diff --git a/Doc/lib/liblogging.tex b/Doc/lib/liblogging.tex
index 639966efc243..eb6fedb1e465 100644
--- a/Doc/lib/liblogging.tex
+++ b/Doc/lib/liblogging.tex
@@ -334,6 +334,20 @@ created, the level is set to \constant{NOTSET} (which causes all messages
 to be processed when the logger is the root logger, or delegation to the
 parent when the logger is a non-root logger). Note that the root logger
 is created with level \constant{WARNING}.
+
+The term "delegation to the parent" means that if a logger has a level
+of NOTSET, its chain of ancestor loggers is traversed until either an
+ancestor with a level other than NOTSET is found, or the root is
+reached.
+
+If an ancestor is found with a level other than NOTSET, then that
+ancestor's level is treated as the effective level of the logger where
+the ancestor search began, and is used to determine how a logging
+event is handled.
+
+If the root is reached, and it has a level of NOTSET, then all
+messages will be processed. Otherwise, the root's level will be used
+as the effective level.
 \end{methoddesc}
 
 \begin{methoddesc}{isEnabledFor}{lvl}