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)
commita7d44001b1f4c3a61c8c96e805034653e268122d (patch)
treed00c459a2cfec66e2500a4382830495b02367e21
parentd913864efaa0b37db07df3d074649093bfae63af (diff)
downloadcpython-a7d44001b1f4c3a61c8c96e805034653e268122d.zip
cpython-a7d44001b1f4c3a61c8c96e805034653e268122d.tar.gz
cpython-a7d44001b1f4c3a61c8c96e805034653e268122d.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 0614402..797bfc2 100644
--- a/Doc/library/logging.rst
+++ b/Doc/library/logging.rst
@@ -121,7 +121,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