diff options
author | Vinay Sajip <vinay_sajip@yahoo.co.uk> | 2012-04-16 14:46:18 (GMT) |
---|---|---|
committer | Vinay Sajip <vinay_sajip@yahoo.co.uk> | 2012-04-16 14:46:18 (GMT) |
commit | 59b9a79a5aa92dcc8f6c36c81394e74083db06de (patch) | |
tree | cfd1829fed51b404f3b24d61f62c08c4a28347b2 /Doc/howto | |
parent | b00e8f108db972b4cbb8f2edc1197d173346979c (diff) | |
download | cpython-59b9a79a5aa92dcc8f6c36c81394e74083db06de.zip cpython-59b9a79a5aa92dcc8f6c36c81394e74083db06de.tar.gz cpython-59b9a79a5aa92dcc8f6c36c81394e74083db06de.tar.bz2 |
Tweaked format of cookbook example.
Diffstat (limited to 'Doc/howto')
-rw-r--r-- | Doc/howto/logging-cookbook.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/Doc/howto/logging-cookbook.rst b/Doc/howto/logging-cookbook.rst index b15c569..66a7e2f 100644 --- a/Doc/howto/logging-cookbook.rst +++ b/Doc/howto/logging-cookbook.rst @@ -1570,10 +1570,10 @@ UTF-8, then you need to do the following: :class:`~logging.handlers.SysLogHandler` instance, with a format string such as:: - u"ASCII section\ufeffUnicode section" + 'ASCII section\ufeffUnicode section' - The Unicode code point ``u'\feff```, when encoded using UTF-8, will be - encoded as a UTF-8 BOM -- the bytestring ``'\xef\xbb\bf'``. + The Unicode code point ``'\feff```, when encoded using UTF-8, will be + encoded as a UTF-8 BOM -- the byte-string ``b'\xef\xbb\xbf'``. #. 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 @@ -1583,8 +1583,8 @@ UTF-8, then you need to do the following: which appears there after substitution is Unicode, that's fine -- it will be encoded using UTF-8. -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 +The formatted message *will* be encoded using UTF-8 encoding by +``SysLogHandler``. If you follow the above rules, you should be able to produce RFC 5424-compliant messages. If you don't, logging may not complain, but your messages will not be RFC 5424-compliant, and your syslog daemon may complain. |