Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

Tweaked format of cookbook example.

This commit is contained in:
Vinay Sajip 2012-04-16 15:45:11 +01:00
parent 4e646aaf93
commit 8085f44844
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
Doc/howto/logging-cookbook.rst
View File

@ -771,10 +771,10 @@ UTF-8, then you need to do the following:
:class:`~logging.handlers.SysLogHandler` instance, with a format string :class:`~logging.handlers.SysLogHandler` instance, with a format string
such as:: such as::
u"ASCII section\ufeffUnicode section" u'ASCII section\ufeffUnicode section'
The Unicode code point ``u'\feff```, when encoded using UTF-8, will be The Unicode code point ``u'\feff```, when encoded using UTF-8, will be
encoded as a UTF-8 BOM -- the bytestring ``'\xef\xbb\bf'``. encoded as a UTF-8 BOM -- the byte-string ``'\xef\xbb\xbf'``.
#. Replace the ASCII section with whatever placeholders you like, but make sure #. Replace the ASCII section with whatever placeholders you like, but make sure
that the data that appears in there after substitution is always ASCII (that that the data that appears in there after substitution is always ASCII (that
@ -785,7 +785,8 @@ UTF-8, then you need to do the following:
encoded using UTF-8. encoded using UTF-8.
If the formatted message is Unicode, it *will* be encoded using UTF-8 encoding If the formatted message is Unicode, it *will* be encoded using UTF-8 encoding
by ``SysLogHandler``. If you follow these rules, you should be able to produce by ``SysLogHandler``. If you follow the above rules, you should be able to
RFC 5424-compliant messages. If you don't, logging may not complain, but your produce RFC 5424-compliant messages. If you don't, logging may not complain,
messages will not be RFC 5424-compliant, and your syslog daemon may complain. but your messages will not be RFC 5424-compliant, and your syslog daemon may
complain.