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 Sworddragon, ezio.melotti, lemburg, loewis, ncoghlan, r.david.murray, serhiy.storchaka, vstinner
Date 2014-06-24.10:08:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <53A94E20.2070909@egenix.com>
In-reply-to <1403603093.16.0.815681756041.issue21331@psf.upfronthosting.co.za>
Content
On 24.06.2014 11:44, Serhiy Storchaka wrote:
> 
> Note that 'raw-unicode-escape' is used in pickle protocol 0. Changing it can break compatibility.

Indeed. unicode-escape was also designed to be able to read back
raw-unicode-escape encoded data, so changing the decoder to not
accept Latin-1 code points would break that as well.

It may be better to simply create a new codec that rejects
non-ASCII encoded bytes when decoding and perhaps call
that 'unicode-repr'.
History
Date User Action Args
2014-06-24 10:08:35lemburgsetrecipients: + lemburg, loewis, ncoghlan, vstinner, ezio.melotti, r.david.murray, Sworddragon, serhiy.storchaka
2014-06-24 10:08:35lemburglinkissue21331 messages
2014-06-24 10:08:35lemburgcreate