Message 368731 - 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.

In-reply-to
Author	petr.viktorin
Recipients	petr.viktorin, vstinner
Date	2020年05月12日.14:09:18
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1589292558.81.0.638694084331.issue40601@roundup.psfhosted.org>

Content
> For example, Objects/longobject.c defines "PyTypeObject PyLong_Type = {...};". This type is exposed in the limited C API (!) Technically, it is not, see https://www.python.org/dev/peps/pep-0384/#structures Structures like PyLong_Type are not part of the limited API. > I propose to break the limited C API backward compatibility on purpose by removing these type definitions form the limited C API. That could only be done in Python 4.0, or if we started C-API 4.0. But I don't think it's necessary here.

Content

> For example, Objects/longobject.c defines "PyTypeObject PyLong_Type = {...};". This type is exposed in the limited C API (!)
Technically, it is not, see https://www.python.org/dev/peps/pep-0384/#structures
Structures like PyLong_Type are *not* part of the limited API.
> I propose to break the limited C API backward compatibility on purpose by removing these type definitions form the limited C API.
That could only be done in Python 4.0, or if we started C-API 4.0. But I don't think it's necessary here.

History
Date	User	Action	Args
2020年05月12日 14:09:18	petr.viktorin	set	recipients: + petr.viktorin, vstinner
2020年05月12日 14:09:18	petr.viktorin	set	messageid: <1589292558.81.0.638694084331.issue40601@roundup.psfhosted.org>
2020年05月12日 14:09:18	petr.viktorin	link	issue40601 messages
2020年05月12日 14:09:18	petr.viktorin	create

homepage