[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`
STINNER Victor
report at bugs.python.org
Thu Mar 3 10:15:22 EST 2022
STINNER Victor <vstinner at python.org> added the comment:
Oh. I didn't know this issue. I recently made changes around PyFrameObject:
* Move PyFrameObject to the internal C API (see bpo-46836 for the rationale)
* Rename CFrame to _PyCFrame
* Rename InterpreterFrame to _PyInterpreterFrame
I prepared PRs for Cython, greenlet and gevent to use the internal C API pycore_frame.h to get the PyFrameObject structure:
https://bugs.python.org/issue46836#msg414283
For the short term, these projects should use the internal C API. But I sent a call to add getter and setter functions:
https://mail.python.org/archives/list/capi-sig@python.org/thread/RCT4SB5LY5UPRRRALEOHWEQHIXFNTHYF/
If possible, it would be great to have a public C API so these projects don't use the internal C API at all, that's being discussed at:
* https://github.com/faster-cpython/ideas/issues/309
* https://bugs.python.org/issue40421
In terms of backward compatibility, since PyFrameObject is now part of the internal C API, we can break things. In practice... it's better to not break 3rd party code too often. See for example Brandt Bucher who is directly impacted by these changes:
https://bugs.python.org/issue46836#msg414279
----------
nosy: +vstinner
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue44800>
_______________________________________
More information about the Python-bugs-list
mailing list