-
-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[C API] Move _PyEval_EvalFrameDefault() to the internal C API #91006
Comments
In Python 3.10, _PyEval_EvalFrameDefault() has the API: PyObject* _PyEval_EvalFrameDefault(PyThreadState *tstate, PyFrameObject *f, int throwflag); In Python 3.11, bpo-44590 (commit ae0a2b7 "Lazily allocate frame objects (GH-27077)") changed it to: PyObject* _PyEval_EvalFrameDefault(PyThreadState *tstate, InterpreterFrame *frame, int throwflag); Problem: InterpreterFrame is part of the internal C API. By the way, PyInterpreterState.eval_frame type (_PyFrameEvalFunction) also changed. This field type already changed in Python 3.9:
Maybe the Python 3.11 change should be documented in What's New in Python 3.11, as it was in What's New in Python 3.9. I propose to move most _PyEval private functions to the internal C API to clarify that they must be used. |
typo: "I propose to move most _PyEval private functions to the internal C API to clarify that they must *NOT* be used." :-) |
See also bpo-46836: "[C API] Move PyFrameObject to the internal C API". |
per https://mail.python.org/archives/list/python-dev@python.org/message/GFOMU7LP63JUVFMWNJNZJLUMZDRPTUYJ/ lets roll some of those PRs back and reshape where we move these APIs as despite the PEP they were not as private as other privates. (deferred blocker meaning: block 3.11beta1 - though Pablo could decide to have the rollbacks block 3.11alpha7) |
The change was rejected by the Steering Council: |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: