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

Skip to content

Commit 59b9a79

Browse files
committed
Tweaked format of cookbook example.
1 parent b00e8f1 commit 59b9a79

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

Doc/howto/logging-cookbook.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1570,10 +1570,10 @@ UTF-8, then you need to do the following:
15701570
:class:`~logging.handlers.SysLogHandler` instance, with a format string
15711571
such as::
15721572

1573-
u"ASCII section\ufeffUnicode section"
1573+
'ASCII section\ufeffUnicode section'
15741574

1575-
The Unicode code point ``u'\feff```, when encoded using UTF-8, will be
1576-
encoded as a UTF-8 BOM -- the bytestring ``'\xef\xbb\bf'``.
1575+
The Unicode code point ``'\feff```, when encoded using UTF-8, will be
1576+
encoded as a UTF-8 BOM -- the byte-string ``b'\xef\xbb\xbf'``.
15771577

15781578
#. Replace the ASCII section with whatever placeholders you like, but make sure
15791579
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:
15831583
which appears there after substitution is Unicode, that's fine -- it will be
15841584
encoded using UTF-8.
15851585

1586-
If the formatted message is Unicode, it *will* be encoded using UTF-8 encoding
1587-
by ``SysLogHandler``. If you follow these rules, you should be able to produce
1586+
The formatted message *will* be encoded using UTF-8 encoding by
1587+
``SysLogHandler``. If you follow the above rules, you should be able to produce
15881588
RFC 5424-compliant messages. If you don't, logging may not complain, but your
15891589
messages will not be RFC 5424-compliant, and your syslog daemon may complain.
15901590

0 commit comments

Comments
 (0)