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 serhiy.storchaka
Recipients ezio.melotti, gvanrossum, kennyluck, lemburg, loewis, pitrou, serhiy.storchaka, tchrist, vstinner
Date 2013-10-08.09:42:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381225339.08.0.987997286064.issue12892@psf.upfronthosting.co.za>
In-reply-to
Content
UTF-16 codec still fast enough. Let first make it correct and then will try optimize it. I have an idea how restore 3.3 performance (if it worth, the code already complicated enough).

The converting to/from wchar_t* uses different code.
History
Date User Action Args
2013-10-08 09:42:19serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, gvanrossum, loewis, pitrou, vstinner, ezio.melotti, tchrist, kennyluck
2013-10-08 09:42:19serhiy.storchakasetmessageid: <1381225339.08.0.987997286064.issue12892@psf.upfronthosting.co.za>
2013-10-08 09:42:19serhiy.storchakalinkissue12892 messages
2013-10-08 09:42:18serhiy.storchakacreate