From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Thu, 29 May 2025 13:44:00 +0000 (+0200)
Subject: [3.13] gh-133260: Remove claim that PyUnicode_InternFromString immortalizes (GH-13421... 
X-Git-Tag: v3.13.4~21
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=a9ba2ecae53e9341a6303d51ccf6b7f0b8160f50;p=thirdparty%2FPython%2Fcpython.git

[3.13] gh-133260: Remove claim that PyUnicode_InternFromString immortalizes (GH-134213) (GH-134884)

(cherry picked from commit 4109a9c6b33faa0032ffc95d96cd0db482af3ce2)

Co-authored-by: Petr Viktorin <encukou@gmail.com>
---

diff --git a/Doc/c-api/unicode.rst b/Doc/c-api/unicode.rst
index 9e679d080fb5..8378f29227a3 100644
--- a/Doc/c-api/unicode.rst
+++ b/Doc/c-api/unicode.rst
@@ -1643,8 +1643,4 @@ They all return ``NULL`` or ``-1`` if an exception occurs.
    from user input, prefer calling :c:func:`PyUnicode_FromString` and
    :c:func:`PyUnicode_InternInPlace` directly.
 
-   .. impl-detail::
-
-      Strings interned this way are made :term:`immortal`.
-