summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2012-02-28 07:21:40 (GMT)
committerGeorg Brandl <georg@python.org>2012-02-28 07:21:40 (GMT)
commite998386442ba491573e6f5cfa43b365f4995d93b (patch)
tree056fe3006028cab4c51bfb6fb4eb442eaa78378d
parentd3113740894d07fefc1ba32b5998a4720e9e8711 (diff)
downloadcpython-e998386442ba491573e6f5cfa43b365f4995d93b.zip
cpython-e998386442ba491573e6f5cfa43b365f4995d93b.tar.gz
cpython-e998386442ba491573e6f5cfa43b365f4995d93b.tar.bz2
Fix markup errors.
-rw-r--r--Doc/howto/logging-cookbook.rst6
1 files changed, 2 insertions, 4 deletions
diff --git a/Doc/howto/logging-cookbook.rst b/Doc/howto/logging-cookbook.rst
index a17d6a3..6f8a693 100644
--- a/Doc/howto/logging-cookbook.rst
+++ b/Doc/howto/logging-cookbook.rst
@@ -1094,7 +1094,7 @@ call to one of the XXXMessage classes.
.. currentmodule:: logging
-.. custom-logrecord:
+.. _custom-logrecord:
Customising ``LogRecord``
-------------------------
@@ -1134,9 +1134,7 @@ The second approach works reasonably well for many cases, but does not allow
you to e.g. use a specialized subclass of :class:`LogRecord`. Library
developers can set a suitable filter on their loggers, but they would have to
remember to do this every time they introduced a new logger (which they would
-do simply by adding new packages or modules and doing
-
-.. code-block:: python
+do simply by adding new packages or modules and doing ::
logger = logging.getLogger(__name__)