From: Vinay Sajip Date: Tue, 6 Jul 2010 15:08:55 +0000 (+0000) Subject: Minor improvements to logging documentation. X-Git-Tag: v2.7.1rc1~640 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=80eed3e625a28f94313512eb8d8dd34d8fb82936;p=thirdparty%2FPython%2Fcpython.git Minor improvements to logging documentation. --- diff --git a/Doc/library/logging.rst b/Doc/library/logging.rst index fbb0935680d5..3a0845d2fe5d 100644 --- a/Doc/library/logging.rst +++ b/Doc/library/logging.rst @@ -248,7 +248,7 @@ With the logger object configured, the following methods create log messages: methods listed above, but this is how to log at custom log levels. :func:`getLogger` returns a reference to a logger instance with the specified -if it is provided, or ``root`` if not. The names are period-separated +name if it is provided, or ``root`` if not. The names are period-separated hierarchical structures. Multiple calls to :func:`getLogger` with the same name will return a reference to the same logger object. Loggers that are further down in the hierarchical list are children of loggers higher up in the list. @@ -1590,6 +1590,11 @@ printed on the console; on the server side, you should see something like:: 69 myapp.area2 WARNING Jail zesty vixen who grabbed pay from quack. 69 myapp.area2 ERROR The five boxing wizards jump quickly. +Note that there are some security issues with pickle in some scenarios. If +these affect you, you can use an alternative serialization scheme by overriding +the :meth:`makePickle` method and implementing your alternative there, as +well as adapting the above script to use your alternative serialization. + Using arbitrary objects as messages -----------------------------------