-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
bpo-46850: Move _PyInterpreterState_SetEvalFrameFunc() to internal C API #32054
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
Conversation
See also PR #32052 "Remove _PyEval_EvalFrameDefault() function". |
According to a code search on top 5000 PyPI project (2022-01-26), two debugger projects are affected, the same projects than the projects affected by PR #32052. debugpy-1.5.1.zip:
ptvsd-4.3.2.zip:
|
This (and PEP-523) is used in TorchDynamo: We (the PyTorch team) are planning to include TorchDynamo as part of PyTorch 2.0. |
PR rebased on top of #32052 that I plan to merge first. |
Move the private _PyFrameEvalFunction type, and private _PyInterpreterState_GetEvalFrameFunc() and _PyInterpreterState_SetEvalFrameFunc() functions to the internal C API. The _PyFrameEvalFunction callback function type now uses the _PyInterpreterFrame type which is part of the internal C API. Update the _PyFrameEvalFunction documentation.
I rely on this API and (other PEP 523 APIs as well) for https://pythonspeed.com/sciagraph/, so would like it or some equivalent to continue to exist. |
This change was reverted: #32343 |
Move the private _PyFrameEvalFunction type, and private
_PyInterpreterState_GetEvalFrameFunc() and
_PyInterpreterState_SetEvalFrameFunc() functions to the internal C
API. The _PyFrameEvalFunction callback function type now uses the
_PyInterpreterFrame type which is part of the internal C API.
Update the _PyFrameEvalFunction documentation.
https://bugs.python.org/issue46850