Uh oh!
There was an error while loading. Please reload this page.
gh-135755: Make Py_TAIL_CALL_INTERP macro private - #138981
Conversation
Rename Py_TAIL_CALL_INTERP to _Py_TAIL_CALL_INTERP.
vstinner
commented
Sep 16, 2025
@Fidget-Spinner: I blindly replaced |
Fidget-Spinner
commented
Sep 16, 2025
Thanks. I'll approve once CI passes. |
vstinner
commented
Sep 16, 2025
I built Python with tail call on Linux using |
Fidget-Spinner
commented
Sep 16, 2025
Don't worry, we have CI for the tail calling interpreter on most platforms, so you can just let it run :) |
vstinner
commented
Sep 17, 2025
Ping @Fidget-Spinner |
vstinner
commented
Sep 17, 2025
@hugovk: This change mostly/only makes sense if it's backported to 3.14. Would you accept this late C API change in 3.14? It makes the macro private. |
vstinner
commented
Sep 18, 2025
Maybe it's ok to leave the macro in 3.14 and remove it in 3.15. No one should rely on this macro :-) |
Uh oh!
There was an error while loading. Please reload this page.
Thanks @vstinner for the PR 🌮🎉.. I'm working now to backport this PR to: 3.14. |
Sorry, @vstinner, I could not cleanly backport this to |
Rename Py_TAIL_CALL_INTERP to _Py_TAIL_CALL_INTERP. (cherry picked from commit 6504f20)
GH-139120 is a backport of this pull request to the 3.14 branch. |
vstinner
commented
Sep 18, 2025
@Fidget-Spinner suggested me to merge this change in the main branch, so I did it :-) |
Rename Py_TAIL_CALL_INTERP to _Py_TAIL_CALL_INTERP.