[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

Mark Shannon added the comment: New changeset 8a349eb30b54bab9a7146fc10e3379c3cacaa19e by Mark Shannon in branch 'main': Revert "bpo-44800: Document internal frame naming conventions (GH-32281)" (#32301) https://github.com/python/cpython/commit/8a349eb30b54bab9a7146fc10e3379c3cacaa19e

[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

Change by Mark Shannon : -- pull_requests: +30363 pull_request: https://github.com/python/cpython/pull/32301 ___ Python tracker ___

[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

Nick Coghlan added the comment: New changeset 124227c95f310d2ecd4b567271ab1919fc7000cb by Nick Coghlan in branch 'main': bpo-44800: Document internal frame naming conventions (GH-32281) https://github.com/python/cpython/commit/124227c95f310d2ecd4b567271ab1919fc7000cb --

[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

Nick Coghlan added the comment: Core dev forum thread: https://discuss.python.org/t/proposal-rename-pyinterpreterframe-struct-as-py-framedata/14213 The conclusion from the forum thread and associated PRs was that any of the further renaming proposed didn't provide sufficient additional

[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

Change by Nick Coghlan : -- pull_requests: +30342 pull_request: https://github.com/python/cpython/pull/32281 ___ Python tracker ___

[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

Change by Nick Coghlan : -- pull_requests: +30113 pull_request: https://github.com/python/cpython/pull/32024 ___ Python tracker ___

[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

Change by Nick Coghlan : -- pull_requests: +30078 pull_request: https://github.com/python/cpython/pull/31987 ___ Python tracker ___

[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

Change by Brandt Bucher : -- nosy: +brandtbucher ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

STINNER Victor 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,

[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

Change by Nick Coghlan : -- pull_requests: +26326 pull_request: https://github.com/python/cpython/pull/3640 ___ Python tracker ___

[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

Nick Coghlan added the comment: >From a naming convention perspective, the code comments and NEWS entry in the >PR now refer to "full frame objects" (``PyFrameObject``) and "frame data >storage structs" (``_Py_framedata``) to avoid giving the misleading impression >that introspection and

[issue44800] Code readability: rename InterpreterFrame to `_Py_framedata`

Nick Coghlan added the comment: PR has been updated with a new API proposal prompted by Mark's review comments on the original proposal. * Rename "pycore_frame.h" to "pycore_framedata.h" * Rename the _interpreter_frame struct to _Py_execution_frame * Rename the type from InterpreterFrame to