➜

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 benjamin.peterson, ezio.melotti, larry, lemburg, ncoghlan, serhiy.storchaka, vstinner, xiang.zhang
Date 2016-10-25.06:53:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <580F0169.7020709@egenix.com>
In-reply-to <1477361810.26.0.09382470018.issue28426@psf.upfronthosting.co.za>
Content 
On 25.10.2016 04:16, Xiang Zhang wrote:
> Marc-Andre, shouldn't the C API of unicode.encode() be PyUnicode_AsEncodedString instead of PyUnicode_AsEncodedUnicode now?

You're right. I got confused with all the slight variations.

> BTW Serhiy, how about PyUnicode_AsEncodedObject? Not see it in your deprecate list.

Let's see what we have:

PyUnicode_AsEncodedString(): encode to bytes (unicode.encode())
PyUnicode_AsEncodedUnicode(): encode to unicode (for e.g. rot13)
PyUnicode_AsEncodedObject(): encode to whatever the codec returns

codecs.encode() can be used for the last two.
History
Date User Action Args
2016-10-25 06:53:33lemburgsetrecipients: + lemburg, ncoghlan, vstinner, larry, benjamin.peterson, ezio.melotti, serhiy.storchaka, xiang.zhang
2016-10-25 06:53:33lemburglinkissue28426 messages
2016-10-25 06:53:33lemburgcreate