Fix markup errors.
This commit is contained in:
parent
d311374089
commit
e998386442
|
@ -1094,7 +1094,7 @@ call to one of the XXXMessage classes.
|
||||||
|
|
||||||
.. currentmodule:: logging
|
.. currentmodule:: logging
|
||||||
|
|
||||||
.. custom-logrecord:
|
.. _custom-logrecord:
|
||||||
|
|
||||||
Customising ``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
|
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
|
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
|
remember to do this every time they introduced a new logger (which they would
|
||||||
do simply by adding new packages or modules and doing
|
do simply by adding new packages or modules and doing ::
|
||||||
|
|
||||||
.. code-block:: python
|
|
||||||
|
|
||||||
logger = logging.getLogger(__name__)
|
logger = logging.getLogger(__name__)
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue