From f2ae79d29e5e0bd24ad1300cb44e3a99104755c7 Mon Sep 17 00:00:00 2001 From: Ned Batchelder Date: Sat, 8 Feb 2025 12:28:35 -0700 Subject: [PATCH] Docs: more explanation of the implications of new tail-call interpreter (GH-129863) Co-authored-by: Ken Jin --- Doc/whatsnew/3.14.rst | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Doc/whatsnew/3.14.rst b/Doc/whatsnew/3.14.rst index 9c4922308b7f..ba7e8b42ef1f 100644 --- a/Doc/whatsnew/3.14.rst +++ b/Doc/whatsnew/3.14.rst @@ -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.) -- 2.47.3