[3.14] gh-133260: Remove claim that PyUnicode_InternFromString immortalizes (GH-13421...

(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 cdd90d05b70b36df33b6337fba66b7d946b12bc3..684432da81c61fb1fe14d5dee1706a30d9c8cfcb 100644 (file)
--- a/Doc/c-api/unicode.rst
+++ b/Doc/c-api/unicode.rst
@@ -1726,10 +1726,6 @@ 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`.
-
 
 .. c:function:: unsigned int PyUnicode_CHECK_INTERNED(PyObject *str)