summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVinay Sajip <vinay_sajip@yahoo.co.uk>2009-10-28 23:28:16 (GMT)
committerVinay Sajip <vinay_sajip@yahoo.co.uk>2009-10-28 23:28:16 (GMT)
commitb6d065ff32427c5dbc5af40e83b545cda8330578 (patch)
treec6b3e6f33996aa31caeddf3840eecba8c77127db
parentb2e796aa27af76bdf0386a34a23415e3efbcc75c (diff)
downloadcpython-b6d065ff32427c5dbc5af40e83b545cda8330578.zip
cpython-b6d065ff32427c5dbc5af40e83b545cda8330578.tar.gz
cpython-b6d065ff32427c5dbc5af40e83b545cda8330578.tar.bz2
Issue 7199: Documentation made slightly more consistent w.r.t. logging level enumeration.
-rw-r--r--Doc/library/logging.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst
index 9dc98fb..5e77e13 100644
--- a/Doc/library/logging.rst
+++ b/Doc/library/logging.rst
@@ -119,7 +119,7 @@ Another useful feature of the logging API is the ability to produce different
messages at different log levels. This allows you to instrument your code with
debug messages, for example, but turning the log level down so that those debug
messages are not written for your production system. The default levels are
-``CRITICAL``, ``ERROR``, ``WARNING``, ``INFO``, ``DEBUG`` and ``NOTSET``.
+``NOTSET``, ``DEBUG``, ``INFO``, ``WARNING``, ``ERROR`` and ``CRITICAL``.
The logger, handler, and log message call each specify a level. The log message
is only emitted if the handler and logger are configured to emit messages of