Description

ncoghlan

opened on Oct 9, 2024

Issue body actions

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.

Linked PRs

• gh-125170: Hard deprecate PyEval_GetLocals in 3.14 #128348

Activity

1. ncoghlan

   added

   interpreter-core(Objects, Python, Grammar, and Parser dirs)(Objects, Python, Grammar, and Parser dirs)

   topic-C-API

   triagedThe issue has been accepted as valid by a triager.The issue has been accepted as valid by a triager.

   3.14bugs and security fixesbugs and security fixes

   on Oct 9, 2024
2. gpshead

   assigned

   markshannon

   on Oct 16, 2024
3. gpshead commented on Oct 16, 2024

   

   gpshead

   on Oct 16, 2024

   Member

   More actions

   (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)
4. xuantengh commented on Nov 6, 2024

   

   xuantengh

   on Nov 6, 2024

   Contributor

   More actions

   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?
5. vstinner commented on Dec 6, 2024

   

   vstinner

   on Dec 6, 2024

   Member

   More actions

   By the way, would it be possible to soft-deprecate or hard-deprecate PyFrame_FastToLocals(), PyFrame_FastToLocalsWithError() and PyFrame_LocalsToFast()?

Issue actions