On Mon, Jan 31, 2022 at 2:31 PM Petr Viktorin <encu...@gmail.com> wrote: > > PEP: 674 > > Title: Disallow using macros as l-value > > The current PEP is named "Disallow using Py_TYPE() and Py_SIZE() macros > as l-values", which is misleading: it proposes to change 65 macros.
Right, I made changes since I posted the "version 2" to python-dev 13 days ago. Since nobody replied to my thread (before you), I directly submitted the latest (updated) PEP to the Steering Council: https://github.com/python/steering-council/issues/100 I decided to put "Py_TYPE() and Py_SIZE()" in the title, since in practice, only these two macros are causing troubles. The PEP changes 65 macros in total. In the latest PEP version, exactly 2 macros are breaking projects: Py_TYPE and Py_SIZE. > > * Allow evolving CPython internals; > > In the current PEP, this is now "Allow evolving CPython internals > (change the PyObject structure);" > > But that's not really true: the PyObject won't become changeable if the > PEP is accepted, since `ob_type` is part of the stable ABI, and direct > access to this field is compiled into existing extensions that use the > stable ABI. When I created https://bugs.python.org/issue39573, I chose the title "Make PyObject an opaque structure in the limited C API". Two years later, I changed the title to "[C API] Avoid accessing PyObject and PyVarObject members directly: add Py_SET_TYPE() and Py_IS_TYPE(), disallow Py_TYPE(obj)=type" since I understood that this project requires multiple incremental steps (and maybe changes should be done in multiple Python versions). You're right that the PEP 674 alone is not enough to fully make the structure opaque. The next interesting problem is that PyType_FromSpec() and PyType_Spec API (which are part of the stable ABI!) use indirectly sizeof(PyObject) in the PyType_Spec.basicsize member. One option to make the PyObject structure opaque would be to modify the PyObject structure to make it empty, and move its members into a new private _PyObject structure. This _PyObject structure would be allocated before the PyObject* pointer, same idea as the current PyGC_Head header which is also allocated before the PyObject* pointer. The main blocker issue is that it breaks the stable ABI. How should the PEP abstract be rephrased to be more accurate? > > On the PyPI top 5000 projects, only 14 projects (0.3%) are affected by 4 > > macro changes. Moreover, 24 projects just have to regenerate their > > Cython code to use ``Py_SET_TYPE()``. > > This data was gathered in 2022. > Since this change was made in 2020 and then reverted because it broke > too many projects (which were presumably notified of the breakage and > had 2 years to update), the 0.3% is misleading. It is a measure of the > current porting effort, not an estimate of the chance of a given project > being affected. I tried to provide all data that I gathered. The following section list 14 projects that had to be fixed: https://www.python.org/dev/peps/pep-0674/#projects-released-with-a-fix I didn't check if they are part of the current top 5000 PyPI project or not. How should the abstract be rephrased to mention these projects? Does someone know how to check if these projects are part of the top 5000 PyPI projects? Victor -- Night gathers, and now my watch begins. It shall not end until my death. _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/BVBXIAMEH3UMDN5NWV4GLRIZ5L4RRI5U/ Code of Conduct: http://python.org/psf/codeofconduct/
