Message368731
| 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> |
| In-reply-to |
| 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 | |