➜

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 vstinner
Recipients methane, serhiy.storchaka, vstinner
Date 2020-06-10.16:09:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1591805352.1.0.263144015623.issue40943@roundup.psfhosted.org>
In-reply-to
Content 
Follow-up of bpo-36381: In Python 3.8, PyArg_ParseTuple() and Py_BuildValue() formats using "int" when PY_SSIZE_T_CLEAN is not defined, but Py_ssize_t when PY_SSIZE_T_CLEAN is defined, were deprecated by:

commit d3c72a223a5f771f964fc34557c55eb5bfa0f5a0
Author: Inada Naoki <songofacandy@gmail.com>
Date:   Sat Mar 23 21:04:40 2019 +0900

    bpo-36381: warn when no PY_SSIZE_T_CLEAN defined (GH-12473)
    
    We will remove int support from 3.10 or 4.0.

I propose to drop support for these formats in Python 3.10. It is a backward incompatible change on purpose, to ensure that all C extensions are compatible with objects larger than 2 GB, and that all C extensions behave the same.

I'm not sure of the effects of this issue on bpo-27499 "PY_SSIZE_T_CLEAN conflicts with Py_LIMITED_API".
History
Date User Action Args
2020-06-10 16:09:12vstinnersetrecipients: + vstinner, methane, serhiy.storchaka
2020-06-10 16:09:12vstinnersetmessageid: <1591805352.1.0.263144015623.issue40943@roundup.psfhosted.org>
2020-06-10 16:09:12vstinnerlinkissue40943 messages
2020-06-10 16:09:11vstinnercreate