traverseda
/
cpython
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merged cookbook corrections from 3.2.

This commit is contained in:
Vinay Sajip 2012-04-17 00:41:39 +01:00
parent bded894499 62930e1cc5
commit f138f8c1ab
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1581,14 +1581,14 @@ following structure: an optional pure-ASCII component, followed by a UTF-8 Byte
Order Mark (BOM), followed by Unicode encoded using UTF-8. (See the `relevant Order Mark (BOM), followed by Unicode encoded using UTF-8. (See the `relevant
section of the specification <http://tools.ietf.org/html/rfc5424#section-6>`_.) section of the specification <http://tools.ietf.org/html/rfc5424#section-6>`_.)
In Python 2.6 and 2.7, code was added to In Python 3.1, code was added to
:class:`~logging.handlers.SysLogHandler` to insert a BOM into the message, but :class:`~logging.handlers.SysLogHandler` to insert a BOM into the message, but
unfortunately, it was implemented incorrectly, with the BOM appearing at the unfortunately, it was implemented incorrectly, with the BOM appearing at the
beginning of the message and hence not allowing any pure-ASCII component to beginning of the message and hence not allowing any pure-ASCII component to
appear before it. appear before it.
As this behaviour is broken, the incorrect BOM insertion code is being removed As this behaviour is broken, the incorrect BOM insertion code is being removed
from Python 2.7.4 and later. However, it is not being replaced, and if you from Python 3.2.4 and later. However, it is not being replaced, and if you
want to produce RFC 5424-compliant messages which includes a BOM, an optional want to produce RFC 5424-compliant messages which includes a BOM, an optional
pure-ASCII sequence before it and arbitrary Unicode after it, encoded using pure-ASCII sequence before it and arbitrary Unicode after it, encoded using
UTF-8, then you need to do the following: UTF-8, then you need to do the following: