Avoid relying on the default reST role in logging library doc

This commit is contained in:
Éric Araujo 2011-11-03 04:35:20 +01:00
parent e2544bc909
commit a083823a85
1 changed files with 4 additions and 4 deletions

View File

@ -137,7 +137,7 @@ instantiated directly, but always through the module-level function
Stack (most recent call last):
This mimics the `Traceback (most recent call last):` which is used when
This mimics the ``Traceback (most recent call last):`` which is used when
displaying exception frames.
The third keyword argument is *extra* which can be used to pass a
@ -820,7 +820,7 @@ functions.
Stack (most recent call last):
This mimics the `Traceback (most recent call last):` which is used when
This mimics the ``Traceback (most recent call last):`` which is used when
displaying exception frames.
The third optional keyword argument is *extra* which can be used to pass a
@ -1059,11 +1059,11 @@ with the :mod:`warnings` module.
If *capture* is ``True``, warnings issued by the :mod:`warnings` module will
be redirected to the logging system. Specifically, a warning will be
formatted using :func:`warnings.formatwarning` and the resulting string
logged to a logger named 'py.warnings' with a severity of `WARNING`.
logged to a logger named ``'py.warnings'`` with a severity of ``'WARNING'``.
If *capture* is ``False``, the redirection of warnings to the logging system
will stop, and warnings will be redirected to their original destinations
(i.e. those in effect before `captureWarnings(True)` was called).
(i.e. those in effect before ``captureWarnings(True)`` was called).
.. seealso::