From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com> Date: Thu, 29 May 2025 13:43:27 +0000 (+0200) Subject: [3.14] gh-133260: Remove claim that PyUnicode_InternFromString immortalizes (GH-13421... X-Git-Tag: v3.14.0b3~138 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2d40dd01faefeabbafbcab510f1934f5e2496796;p=thirdparty%2FPython%2Fcpython.git [3.14] gh-133260: Remove claim that PyUnicode_InternFromString immortalizes (GH-134213) (GH-134883) (cherry picked from commit 4109a9c6b33faa0032ffc95d96cd0db482af3ce2) Co-authored-by: Petr Viktorin --- diff --git a/Doc/c-api/unicode.rst b/Doc/c-api/unicode.rst index cdd90d05b70b..684432da81c6 100644 --- 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)