Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
f138f8c1
Commit
f138f8c1
authored
Apr 17, 2012
by
Vinay Sajip
Browse files
Options
Browse Files
Download
Plain Diff
Merged cookbook corrections from 3.2.
parents
bded8944
62930e1c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
Doc/howto/logging-cookbook.rst
Doc/howto/logging-cookbook.rst
+2
-2
No files found.
Doc/howto/logging-cookbook.rst
View file @
f138f8c1
...
@@ -1581,14 +1581,14 @@ following structure: an optional pure-ASCII component, followed by a UTF-8 Byte
...
@@ -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:
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment