Jan 23, 2026 · Jan 24, 2026 · Jan 24, 2026 · Jan 24, 2026 · Jan 24, 2026 · Jan 24, 2026
diff --git a/Doc/c-api/unicode.rst b/Doc/c-api/unicode.rst
   :c:expr:`PyUnicode_CheckExact(*p_unicode)` must be true. If it is not,
   then -- as with any other error -- the argument is left unchanged.

 Note thatinternedstringsare not“immortal”.
 Stringsinternedby this functionare not:term:`immortal`.
   You must keep a reference to the result to benefit from interning.

   .. note::
      On the :term:`free threaded <free threading>` build,
      all interned strings are :term:`immortal`.
      This may change in the future.

 .. c:function:: PyObject* PyUnicode_InternFromString(const char *str)

diff --git a/Doc/howto/free-threading-python.rst b/Doc/howto/free-threading-python.rst
 Immortalization
 ---------------

 In the free-threaded build,some objects are:term:`immortal`.
 On the free-threaded build,more objects aremadeimmortal.
 Immortal objects are not deallocated and have reference counts that are
 never modified.  This is done to avoid reference count contention that would
 prevent efficient multi-threaded scaling.

 As of the 3.14 release, immortalization is limited to:
 As of the 3.14 release,this additionalimmortalization is limited to:

 * Code constants: numeric literals, string literals, and tuple literals
  composed of other constants.
diff --git a/Doc/library/sys.rst b/Doc/library/sys.rst
   Interned strings are not :term:`immortal`; you must keep a reference to the
   return value of :func:`intern` around to benefit from it.

   .. note::
      On the :term:`free threaded <free threading>` build,
      all interned strings are :term:`immortal`.
      This may change in the future.

 .. function:: _is_gil_enabled()
Original file line number	Diff line number	Diff line change
Expand Up		@@ -1750,9 +1750,13 @@ They all return ``NULL`` or ``-1`` if an exception occurs.
		:c:expr:`PyUnicode_CheckExact(*p_unicode)` must be true. If it is not,
		then -- as with any other error -- the argument is left unchanged.

		Note thatinternedstringsare not“immortal”.
		Stringsinternedby this functionare not:term:`immortal`.
		You must keep a reference to the result to benefit from interning.

		.. note::
		On the :term:`free threaded <free threading>` build,
		all interned strings are :term:`immortal`.
		This may change in the future.

		.. c:function:: PyObject* PyUnicode_InternFromString(const char *str)

Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -99,12 +99,12 @@ This section describes known limitations of the free-threaded CPython build.
		Immortalization
		---------------

		In the free-threaded build,some objects are:term:`immortal`.
		On the free-threaded build,more objects aremadeimmortal.
		Immortal objects are not deallocated and have reference counts that are
		never modified. This is done to avoid reference count contention that would
		prevent efficient multi-threaded scaling.

		As of the 3.14 release, immortalization is limited to:
		As of the 3.14 release,this additionalimmortalization is limited to:

		* Code constants: numeric literals, string literals, and tuple literals
		composed of other constants.
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -1325,6 +1325,10 @@ always available. Unless explicitly noted otherwise, all variables are read-only
		Interned strings are not :term:`immortal`; you must keep a reference to the
		return value of :func:`intern` around to benefit from it.

		.. note::
		On the :term:`free threaded <free threading>` build,
		all interned strings are :term:`immortal`.
		This may change in the future.

		.. function:: _is_gil_enabled()

Expand Down