This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients docs@python, ezio.melotti, lemburg, vstinner, zuo
Date 2013-11-11.19:19:22
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Jan, the codec implements an encoding which has certain characteristics just like any other codec. It works both in Python 2 and 3 without problems.

The documentation is no longer true, though. Ever since we added encoding markers to source files, the raw Unicode string literals depended on this encoding setting. Before this change the docs were fine, since Unicode literals were interpreted as Latin-1 encoded.

More correct would be: "Produce a string that uses Unicode escapes to encode non-Latin-1 code points. It is used in the Python pickle protocol."
Date User Action Args
2013-11-11 19:19:23lemburgsetrecipients: + lemburg, vstinner, ezio.melotti, zuo, docs@python
2013-11-11 19:19:23lemburgsetmessageid: <>
2013-11-11 19:19:23lemburglinkissue19539 messages
2013-11-11 19:19:22lemburgcreate