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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, doerwalter, eric.smith, ezio.melotti, flox, lemburg, vstinner
Date 2010-02-24.09:44:00
SpamBayes Score 6.839487e-07
Marked as misclassified No
Message-id <1267004642.18.0.456785037879.issue7649@psf.upfronthosting.co.za>
In-reply-to
Content
> Could you please check for chars above 0x7f first and then use
> PyUnicode_Decode() instead of the PyUnicode_FromStringAndSize() API

I concur: PyUnicode_FromStringAndSize() decodes with utf-8 whereas the expected conversion char->unicode should use the default encoding (ascii).
But why is it necessary to check for chars above 0x7f?

> (this API should not have been backported from the Python 3.x
> in Python 2.6,
This function is still useful when the chars come from a C string literal in the source code (btw there should be something about the encoding used in C files). But it's not always correctly used even in 3.x, in posixmodule.c for example.
History
Date User Action Args
2010-02-24 09:44:02amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, lemburg, doerwalter, vstinner, eric.smith, ezio.melotti, flox
2010-02-24 09:44:02amaury.forgeotdarcsetmessageid: <1267004642.18.0.456785037879.issue7649@psf.upfronthosting.co.za>
2010-02-24 09:44:00amaury.forgeotdarclinkissue7649 messages
2010-02-24 09:44:00amaury.forgeotdarccreate