From df7a22568bc4e944fd37a41ebf1f2740ff54976d Mon Sep 17 00:00:00 2001 From: Tanya Schlusser Date: Sat, 17 Jan 2015 21:43:22 -0600 Subject: [PATCH] Italic pro/con to bold, and '--' to colon after the pro/con --- docs/writing/logging.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/writing/logging.rst b/docs/writing/logging.rst index 0cee15d..70e20de 100644 --- a/docs/writing/logging.rst +++ b/docs/writing/logging.rst @@ -83,19 +83,19 @@ application environment. There are at least three ways to configure a logger: - Using an INI-formatted file: - - *Pro* -- possible to update configuration while running + - **Pro**: possible to update configuration while running using the function :func:`logging.config.listen` to listen on a socket. - - *Con* -- less control (*e.g.* custom subclassed filters or loggers) + - **Con**: less control (*e.g.* custom subclassed filters or loggers) than possible when configuring a logger in code. - Using a dictionary or a JSON-formatted file: - - *Pro* -- in addition to updating while running, it is possible to + - **Pro**: in addition to updating while running, it is possible to load from a file using the :mod:`json` module, in the standard library since Python 2.6. - - *Con* -- less control than when configuring a logger in code. + - **Con**: less control than when configuring a logger in code. - Using code: - - *Pro* -- complete control over the configuration. - - *Con* -- modifications require a change to source code. + - **Pro**: complete control over the configuration. + - **Con**: modifications require a change to source code. Example Configuration via an INI File