gh-119786: Remove mention of _PyThreadState_BumpFramePointer from InternalDocs/interpreter.md#141816
Conversation
Co-authored-by: Irit Katriel <1055913+iritkatriel@users.noreply.github.com>
|
how far back does this needs back porting? |
Sorry, something went wrong.
|
Thx for the review, @iritkatriel! Backporting to 3.13 and 3.14 seems to be optimal, since this change was landed to 3.12, and docs changes are definitely not a security fixes. |
Sorry, something went wrong.
|
we can back port doc updates to security fix versions |
Sorry, something went wrong.
|
Actually, we can backport only to 3.14, since there's no |
Sorry, something went wrong.
cf7a309
into
python:main
Dec 16, 2025
|
Thanks @efimov-mikhail for the PR, and @hugovk for merging it 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Sorry, something went wrong.
…from `InternalDocs/interpreter.md` (pythonGH-141816) (cherry picked from commit cf7a309) Co-authored-by: Mikhail Efimov <efimov.mikhail@gmail.com> Co-authored-by: Irit Katriel <1055913+iritkatriel@users.noreply.github.com>
In #93908 function
_PyThreadState_BumpFramePointerwas removed.But we still have its mention in
InternalDocs/interpreter.md.I propose to remove it and slightly change wording around.
For example, functions
_PyThreadState_HasStackSpaceand_PyFrame_PushUncheckedcould be mentioned.CC @iritkatriel @markshannon