➜

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 ezio.melotti, gvanrossum, kennyluck, lemburg, loewis, pitrou, serhiy.storchaka, tchrist, vstinner
Date 2013-10-08.10:39:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <5253E0C5.3010606@egenix.com>
In-reply-to <851275436.59250047.1381228250501.JavaMail.root@zimbra10-e2.priv.proxad.net>
Content 
On 08.10.2013 12:30, Antoine Pitrou wrote:
> 
>> UTF-8, UTF-16 and UTF-32 codecs need to be as fast as possible
>> in Python to not create performance problems when converting
>> between platform Unicode data and the internal formats
>> used in Python.
> 
> "As fast as possible" is a platonic dream.
> They only need to be fast enough not to be bottlenecks.

No, they need to be as fast as possible, without sacrificing
correctness.

This has always been our guideline for codec implementations
and string methods. As a result, our implementations are some
of the best out there.
History
Date User Action Args
2013-10-08 10:39:06lemburgsetrecipients: + lemburg, gvanrossum, loewis, pitrou, vstinner, ezio.melotti, tchrist, kennyluck, serhiy.storchaka
2013-10-08 10:39:06lemburglinkissue12892 messages
2013-10-08 10:39:06lemburgcreate