Message 308506 - Python tracker

➜

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	ideasman42
Recipients	ezio.melotti, ideasman42, vstinner
Date	2017-12-18.02:00:11
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1513562412.88.0.213398074469.issue32354@psf.upfronthosting.co.za>
In-reply-to

Content
Py_UNICODE_TOLOWER / Py_UNICODE_TOUPPER are marked as deprecated in the docs. https://docs.python.org/3/c-api/unicode.html?highlight=py_unicode_tolower#c.Py_UNICODE_TOLOWER Someone submitted a patch to our project which uses these. What is unclear, is if there is an intention to replace these (wrappers for '_PyUnicode_ToLowerFull' for eg). Or if this will be removed without any alternative. I assume the functionality will be kept somewhere since Python needs str.lower/upper. Will there be a way to perform this in the future? Either way, could docs be updated to reflect this?

Py_UNICODE_TOLOWER / Py_UNICODE_TOUPPER are marked as deprecated in the docs.

https://docs.python.org/3/c-api/unicode.html?highlight=py_unicode_tolower#c.Py_UNICODE_TOLOWER

Someone submitted a patch to our project which uses these.

What is unclear, is if there is an intention to replace these (wrappers for '_PyUnicode_ToLowerFull' for eg).

Or if this will be removed without any alternative.

I assume the functionality will be kept somewhere since Python needs str.lower/upper.

Will there be a way to perform this in the future? Either way, could docs be updated to reflect this?

History
Date	User	Action	Args
2017-12-18 02:00:12	ideasman42	set	recipients: + ideasman42, vstinner, ezio.melotti
2017-12-18 02:00:12	ideasman42	set	messageid: <1513562412.88.0.213398074469.issue32354@psf.upfronthosting.co.za>
2017-12-18 02:00:12	ideasman42	link	issue32354 messages
2017-12-18 02:00:11	ideasman42	create