add whatsnew entry for PyUnstable_SetImmortal and PyDatetime_IMPORT (#144830)

This commit is contained in:
Kumar Aditya 2026-02-15 20:21:54 +05:30 committed by GitHub
parent e6110efd03
commit 50c479e613
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 14 additions and 0 deletions

View file

@ -30,6 +30,10 @@ macros.
This is not compatible with subinterpreters.
.. versionchanged:: 3.15
This macro is now thread safe.
.. c:type:: PyDateTime_CAPI
Structure containing the fields for the datetime C API.
@ -44,6 +48,11 @@ macros.
This variable is only available once :c:macro:`PyDateTime_IMPORT` succeeds.
.. versionchanged:: 3.15
This variable should not be accessed directly as direct access is not thread-safe.
Use :c:func:`PyDateTime_IMPORT` instead.
.. c:type:: PyDateTime_Date
This subtype of :c:type:`PyObject` represents a Python date object.

View file

@ -1563,6 +1563,8 @@ New features
thread state.
(Contributed by Victor Stinner in :gh:`139653`.)
* Add :c:func:`PyUnstable_SetImmortal` C-API function to mark objects as :term:`immortal`.
(Contributed by Kumar Aditya in :gh:`143300`.)
Changed C APIs
--------------
@ -1571,6 +1573,9 @@ Changed C APIs
flag is set then :c:macro:`Py_TPFLAGS_HAVE_GC` must be set too.
(Contributed by Sergey Miryanov in :gh:`134786`.)
* :c:macro:`PyDateTime_IMPORT` is now thread safe. Code that directly checks ``PyDateTimeAPI``
for ``NULL`` should be updated to call :c:macro:`PyDateTime_IMPORT` instead.
(Contributed by Kumar Aditya in :gh:`141563`.)
Porting to Python 3.15
----------------------