diff options
author | Vinay Sajip <vinay_sajip@yahoo.co.uk> | 2012-04-17 00:40:48 +0100 |
---|---|---|
committer | Vinay Sajip <vinay_sajip@yahoo.co.uk> | 2012-04-17 00:40:48 +0100 |
commit | d9b1fa28fcc138da954ad2a78426cb344aa18b95 (patch) | |
tree | 994954fb4fec504839b7ba623273f1a34b130ae7 /Doc | |
parent | 0410df697a43929ceedb1ad366170a9f0816007e (diff) | |
download | cpython-d9b1fa28fcc138da954ad2a78426cb344aa18b95.tar.gz |
Corrected version numbers in cookbook example.
Diffstat (limited to 'Doc')
-rw-r--r-- | Doc/howto/logging-cookbook.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Doc/howto/logging-cookbook.rst b/Doc/howto/logging-cookbook.rst index 66a7e2f922..59864a9adc 100644 --- a/Doc/howto/logging-cookbook.rst +++ b/Doc/howto/logging-cookbook.rst @@ -1554,14 +1554,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 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 unfortunately, it was implemented incorrectly, with the BOM appearing at the beginning of the message and hence not allowing any pure-ASCII component to appear before it. 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 pure-ASCII sequence before it and arbitrary Unicode after it, encoded using UTF-8, then you need to do the following: |