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 t2y
Recipients ishimoto, lemburg, loewis, methane, r.david.murray, serhiy.storchaka, t2y, vstinner
Date 2014-12-15.17:21:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAGBzy2rpf4ZD=v5O7jwDc+0sRdZ+drHpfP0a_Bnoy=-hanFUuw@mail.gmail.com>
In-reply-to <1418661957.65.0.00216039629905.issue23050@psf.upfronthosting.co.za>
Content
>> These character encodings are legacy, but are still used.
>
> Do you have an idea of how many users still have documents stored or exchanged using these encodings?

Hmm, I guess iso-2022-jp codec is still default charset of MUA (Mail
User Agent) on Japanese Windows platform. But I'm not sure how many so
I'll investigate, wait a few days.

> The patch is not trivial, the legacy japanese codecs are complex and so error prone :-/

Ya, this patch has some refactoring. However, existing tests have
passed and adding encoding codecs wouldn't affect other codecs
basically. Why do you think it's "error plone"?

> For previous requests to add new codecs, we closed issues as wontfix and we suggested to share the codecs at the Python Cheeseshop (PyPI). Here it's more complex because C code is modified to implement the new encodings.

Could you show me previous requests? I can understand C code modifying
is higher cost to review. However, we have codec tests and it wouldn't
affect other codecs, I think.
History
Date User Action Args
2014-12-15 17:21:59t2ysetrecipients: + t2y, lemburg, loewis, ishimoto, vstinner, r.david.murray, methane, serhiy.storchaka
2014-12-15 17:21:59t2ylinkissue23050 messages
2014-12-15 17:21:59t2ycreate