http://hg.python.org/cpython/rev/5c8130b85c17 changeset: 87660:5c8130b85c17 branch: 3.3 parent: 87656:b92f9eaedb76 user: Vinay Sajip <vinay_sajip@yahoo.co.uk> date: Sat Nov 30 22:45:29 2013 +0000 summary: Issue #19789: Clarified documentation for logging.disable. files: Doc/library/logging.rst | 6 ++++-- 1 files changed, 4 insertions(+), 2 deletions(-) diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst --- a/Doc/library/logging.rst +++ b/Doc/library/logging.rst @@ -987,8 +987,10 @@ effect is to disable all logging calls of severity *lvl* and below, so that if you call it with a value of INFO, then all INFO and DEBUG events would be discarded, whereas those of severity WARNING and above would be processed - according to the logger's effective level. To undo the effect of a call to - ``logging.disable(lvl)``, call ``logging.disable(logging.NOTSET)``. + according to the logger's effective level. If + ``logging.disable(logging.NOTSET)`` is called, it effectively removes this + overriding level, so that logging output again depends on the effective + levels of individual loggers. .. function:: addLevelName(lvl, levelName) -- Repository URL: http://hg.python.org/cpython