You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
PEP 667 follow-up: hard deprecate PyEval_GetLocals() #125170
During the lead up to the 3.13.0 release, the SC approved an amendment to PEP 667 that escalates Python 3.13's soft deprecation for PyEval_GetLocals() to a hard deprecation in 3.14 for eventual removal in 3.16 (the difficulties of keeping that API working in the face of the other implementation changes made the fundamental flaws in the way this API works more self-evident).
This ticket covers adding the hard deprecation to the C code and the expected removal version to the C API docs.
Hi I would like to kindly ask whether I can take this issue? To hard deprecate a function, we may need to warn a PyExc_DeprecationWarning and declare the function with Py_DEPRECATED?
By the way, would it be possible to soft-deprecate or hard-deprecate PyFrame_FastToLocals(), PyFrame_FastToLocalsWithError() and PyFrame_LocalsToFast()?
Activity
gpshead commentedon Oct 16, 2024
(I assigned this to mark based on the comment pointing here but maybe this one isn't for mark specifically, feel free to un/reassign)
xuantengh commentedon Nov 6, 2024
Hi I would like to kindly ask whether I can take this issue? To hard deprecate a function, we may need to warn a
PyExc_DeprecationWarningand declare the function withPy_DEPRECATED?vstinner commentedon Dec 6, 2024
By the way, would it be possible to soft-deprecate or hard-deprecate PyFrame_FastToLocals(), PyFrame_FastToLocalsWithError() and PyFrame_LocalsToFast()?