Skip to content

Docs: more explanation of the implications of new tail-call interpreter #129863

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Feb 8, 2025
Merged

Docs: more explanation of the implications of new tail-call interpreter #129863

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ea1662d
Docs: more explanation of the implications of new tail-call interpreter
nedbat Feb 8, 2025
eb3661a
Update Doc/whatsnew/3.14.rst
nedbat Feb 8, 2025
efbb503
Update Doc/whatsnew/3.14.rst
Fidget-Spinner Feb 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion Doc/whatsnew/3.14.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -235,9 +235,13 @@ For further information on how to build Python, see
This is not to be confused with `tail call optimization`__ of Python
functions, which is currently not implemented in CPython.

This new interpreter type is an internal implementation detail of the CPython
interpreter. It doesn't change the visible behavior of Python programs at
all. It can improve their performance, but doesn't change anything else.

__ https://en.wikipedia.org/wiki/Tail_call

(Contributed by Ken Jin in :gh:`128718`, with ideas on how to implement this
(Contributed by Ken Jin in :gh:`128563`, with ideas on how to implement this
in CPython by Mark Shannon, Garrett Gu, Haoran Xu, and Josh Haberman.)


Expand Down
Loading