From e998386442ba491573e6f5cfa43b365f4995d93b Mon Sep 17 00:00:00 2001 From: Georg Brandl Date: Tue, 28 Feb 2012 08:21:40 +0100 Subject: [PATCH] Fix markup errors. --- Doc/howto/logging-cookbook.rst | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/Doc/howto/logging-cookbook.rst b/Doc/howto/logging-cookbook.rst index a17d6a36475..6f8a693650e 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__)