➜

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.

Author ncoghlan
Recipients Mark.Shannon, brandtbucher, ncoghlan, pablogsal, vstinner
Date 2022-04-03.05:27:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1648963648.11.0.526913878021.issue44800@roundup.psfhosted.org>
In-reply-to
Content 
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 clarity to justify further code churn in a semi public API.

 As a result, the final PR just documents the status quo in the internal C API frame header (since the conventions arising from the code-churn-minimising migration to a split data structure is hard to infer just from reading the code): https://github.com/python/cpython/pull/32281
History
Date User Action Args
2022-04-03 05:27:28ncoghlansetrecipients: + ncoghlan, vstinner, Mark.Shannon, pablogsal, brandtbucher
2022-04-03 05:27:28ncoghlansetmessageid: <1648963648.11.0.526913878021.issue44800@roundup.psfhosted.org>
2022-04-03 05:27:28ncoghlanlinkissue44800 messages
2022-04-03 05:27:27ncoghlancreate