Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit c15dfd6

Browse files
committed
Minor improvements to logging documentation.
1 parent 6f493b7 commit c15dfd6

1 file changed

Lines changed: 6 additions & 1 deletion

File tree

Doc/library/logging.rst

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -246,7 +246,7 @@ With the logger object configured, the following methods create log messages:
246246
methods listed above, but this is how to log at custom log levels.
247247

248248
:func:`getLogger` returns a reference to a logger instance with the specified
249-
if it is provided, or ``root`` if not. The names are period-separated
249+
name if it is provided, or ``root`` if not. The names are period-separated
250250
hierarchical structures. Multiple calls to :func:`getLogger` with the same name
251251
will return a reference to the same logger object. Loggers that are further
252252
down in the hierarchical list are children of loggers higher up in the list.
@@ -1572,6 +1572,11 @@ printed on the console; on the server side, you should see something like::
15721572
69 myapp.area2 WARNING Jail zesty vixen who grabbed pay from quack.
15731573
69 myapp.area2 ERROR The five boxing wizards jump quickly.
15741574

1575+
Note that there are some security issues with pickle in some scenarios. If
1576+
these affect you, you can use an alternative serialization scheme by overriding
1577+
the :meth:`makePickle` method and implementing your alternative there, as
1578+
well as adapting the above script to use your alternative serialization.
1579+
15751580
Using arbitrary objects as messages
15761581
-----------------------------------
15771582

0 commit comments

Comments
 (0)