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, vstinner
Date 2010-09-07.23:54:08
SpamBayes Score 6.099713e-08
Marked as misclassified No
Message-id <1283903653.58.0.315895543376.issue9769@psf.upfronthosting.co.za>
In-reply-to
Content
> > PyUnicode_FromFormat("%s", text) expects a utf-8 buffer.
> Really?

The *format* looks more like latin-1, right. But the payload of a "%s" item is decoded as utf-8.

> I don't think that a C file calls PyErr_Format() or
> PyUnicode_FromFormat(V)() with a non-ascii format string.

At the moment, it's true. My remark is that utf-8 tend to be applied to all kind of files; if someone once decide that non-ascii chars are allowed in (some) string constants, they will be stored in utf-8.
History
Date User Action Args
2010-09-07 23:54:13amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, vstinner
2010-09-07 23:54:13amaury.forgeotdarcsetmessageid: <1283903653.58.0.315895543376.issue9769@psf.upfronthosting.co.za>
2010-09-07 23:54:09amaury.forgeotdarclinkissue9769 messages
2010-09-07 23:54:09amaury.forgeotdarccreate