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 lemburg, pitrou, vstinner
Date 2010-06-10.10:34:59
SpamBayes Score 0.012138328
Marked as misclassified No
Message-id <4C10BFD2.5000702@egenix.com>
In-reply-to <1275949981.66.0.571681325081.issue8922@psf.upfronthosting.co.za>
Content
STINNER Victor wrote:
> 
> STINNER Victor <victor.stinner@haypocalc.com> added the comment:
> 
>> Note that these shortcut bypass the codec registry logic.
> 
> Yes, but it's already the case without my patch. I don't think that it's really useful to override latin1, utf-8, utf-16, utf-32 or mbcs. I prefer a faster Python :-) 

Depends on your use case. E.g. utf-32 is hardly ever used in practice,
utf-16 is only common on Windows and then only as utf-16-le,
I'm not sure about mbcs since that's a meta-codec. In reality, this
will likely be the same as cp1252 most of the time.

I'm ok on ascii, latin1, utf-8 and mbcs (including the additional
normalization, aliasiing and case mapping), but not on the others.

>> we have to be careful about adding more such shortcuts.
> 
> I just want to add a shortcut for ISO-8859-1.

Fine, even though that name is really not used much in Python code.
History
Date User Action Args
2010-06-10 10:35:02lemburgsetrecipients: + lemburg, pitrou, vstinner
2010-06-10 10:35:00lemburglinkissue8922 messages
2010-06-10 10:34:59lemburgcreate