From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Wed, 18 Oct 2023 23:22:03 +0000 (+0200)
Subject: [3.12] GH-104232: Fix statement about trace return values (GH-111047)
X-Git-Tag: v3.12.1~267
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=9ef8caf293b6a54f73fb66e3eca653783b3e0f28;p=thirdparty%2FPython%2Fcpython.git

[3.12] GH-104232: Fix statement about trace return values (GH-111047)

(cherry picked from commit d9246c7b734b8958da03494045208681d95f5b74)
---

diff --git a/Doc/library/sys.rst b/Doc/library/sys.rst
index 6fb4c0f1c538..3782d1e6c6f2 100644
--- a/Doc/library/sys.rst
+++ b/Doc/library/sys.rst
@@ -1552,9 +1552,8 @@ always available.
    function to be used for the new scope, or ``None`` if the scope shouldn't be
    traced.
 
-   The local trace function should return a reference to itself (or to another
-   function for further tracing in that scope), or ``None`` to turn off tracing
-   in that scope.
+   The local trace function should return a reference to itself, or to another
+   function which would then be used as the local trace function for the scope.
 
    If there is any error occurred in the trace function, it will be unset, just
    like ``settrace(None)`` is called.