Message 278552 - Python tracker [proxy]

[proxy] bugs.python.org — ← back | site home | direct (HTTPS) ↗ | proxy home | ◑ dark◐ light

➜

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, lemburg, ncoghlan, serhiy.storchaka, vstinner, xiang.zhang
Date	2016-10-13.08:22:17
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<57FF4432.1050202@egenix.com>
In-reply-to	<1476346221.15.0.496435555399.issue28426@psf.upfronthosting.co.za>

Content
On 13.10.2016 10:10, Serhiy Storchaka wrote: > Shouldn't all these function be deprecated in favour of PyCodec_*() APIs? Not all of them, since you still want to have a C API for unicode.encode(). PyUnicode_AsEncodedUnicode() would have to stay. As for the others, I don't know how much use they get.

On 13.10.2016 10:10, Serhiy Storchaka wrote:
> Shouldn't all these function be deprecated in favour of PyCodec_*() APIs?

Not all of them, since you still want to have a C API for
unicode.encode(). PyUnicode_AsEncodedUnicode() would have
to stay.

As for the others, I don't know how much use they get.

History
Date	User	Action	Args
2016-10-13 08:22:18	lemburg	set	recipients: + lemburg, ncoghlan, vstinner, benjamin.peterson, ezio.melotti, serhiy.storchaka, xiang.zhang
2016-10-13 08:22:18	lemburg	link	issue28426 messages
2016-10-13 08:22:17	lemburg	create