➜

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 vstinner
Recipients eryksun, ezio.melotti, lazka, terry.reedy, vstinner, xiang.zhang
Date 2016-09-09.23:38:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAMpsgwbv2TxuDWkZT4iLOS_mdZvX-_ABX6y-YM=J33p3WL0+WA@mail.gmail.com>
In-reply-to <1473461811.01.0.594860974175.issue27971@psf.upfronthosting.co.za>
Content 
> Considering the UTF-16 codec isn't self-consistent, it's a stretch to say it's not a bug.

I didn't say that it's not a bug. I said that it's not possible to
modify a codec at this point in Python 2.7 without taking a risk of
breaking applications relying on the current behaviour. Even in Python
3, we don't do such change in minor releases, but only in major
releases.
History
Date User Action Args
2016-09-09 23:38:09vstinnersetrecipients: + vstinner, terry.reedy, ezio.melotti, eryksun, xiang.zhang, lazka
2016-09-09 23:38:09vstinnerlinkissue27971 messages
2016-09-09 23:38:09vstinnercreate