bpo-46850: Move _PyInterpreterState_SetEvalFrameFunc() to internal C API#32054
bpo-46850: Move _PyInterpreterState_SetEvalFrameFunc() to internal C API#32054vstinner merged 1 commit into
Conversation
|
See also PR #32052 "Remove _PyEval_EvalFrameDefault() function". |
Sorry, something went wrong.
|
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: |
Sorry, something went wrong.
|
This (and PEP-523) is used in TorchDynamo: We (the PyTorch team) are planning to include TorchDynamo as part of PyTorch 2.0. |
Sorry, something went wrong.
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. |
Sorry, something went wrong.
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