summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVinay Sajip <vinay_sajip@yahoo.co.uk>2012-05-20 14:37:33 (GMT)
committerVinay Sajip <vinay_sajip@yahoo.co.uk>2012-05-20 14:37:33 (GMT)
commit07162d4142cb755a6a9af2999b995e7bd9cb75b2 (patch)
tree7dc36e6a20a5827d39dccd4d38b3be8c8ea6fb19
parenta1df1cc767650eb45bb869df692ac381c43de4af (diff)
parent69d8493899592c64c0297964d7addb91aaeb0f17 (diff)
downloadcpython-07162d4142cb755a6a9af2999b995e7bd9cb75b2.zip
cpython-07162d4142cb755a6a9af2999b995e7bd9cb75b2.tar.gz
cpython-07162d4142cb755a6a9af2999b995e7bd9cb75b2.tar.bz2
Closes #14864: Added documentation on how to undo the effects of a logging.disable() call. Thanks to user Guillaume for the suggestion.
-rw-r--r--Doc/library/logging.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst
index d533c9a..fbbd305 100644
--- a/Doc/library/logging.rst
+++ b/Doc/library/logging.rst
@@ -962,7 +962,8 @@ 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.
+ according to the logger's effective level. To undo the effect of a call to
+ ``logging.disable(lvl)``, call ``logging.disable(logging.NOTSET)``.
.. function:: addLevelName(lvl, levelName)