]> granicus.if.org Git - python/commitdiff
Issue #19789: Clarified documentation for logging.disable.
authorVinay Sajip <vinay_sajip@yahoo.co.uk>
Sat, 30 Nov 2013 22:43:13 +0000 (22:43 +0000)
committerVinay Sajip <vinay_sajip@yahoo.co.uk>
Sat, 30 Nov 2013 22:43:13 +0000 (22:43 +0000)
Doc/library/logging.rst

index f3fda14f7fc353201035c32ef7f536ea498d6146..68e359e61a34278cba8988bc3038e4031e9c7a4f 100644 (file)
@@ -837,8 +837,10 @@ functions.
    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)