Skip to content

Commit ae437f1

Browse files
committed
Fix up docs
1 parent a155802 commit ae437f1

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

Doc/c-api/tuple.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,7 @@ Tuple Objects
8686
8787
Insert a reference to object *o* at position *pos* of the tuple pointed to by
8888
*p*. Return ``0`` on success. If *pos* is out of bounds, return ``-1``
89-
and set an :exc:`IndexError` exception.
89+
and set an :exc:`IndexError` exception. Both ``p`` and ``o`` must be non-``NULL``.
9090
9191
.. note::
9292

Doc/whatsnew/3.13.rst

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2661,10 +2661,6 @@ Changes in the C API
26612661

26622662
Note that ``Py_TRASHCAN_BEGIN`` has a second argument which
26632663
should be the deallocation function it is in. The new macros were
2664-
* The :c:func:`PyTuple_SET_ITEM` inline function may not be passed ``NULL``.
2665-
This has always been the documented behavior, but was not enforced for
2666-
the value until now. :c:var:``Py_None` should be used instead of ``NULL``.
2667-
26682664
added in Python 3.8 and the old macros were deprecated in Python 3.11.
26692665
(Contributed by Irit Katriel in :gh:`105111`.)
26702666

Doc/whatsnew/3.14.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -827,6 +827,10 @@ Porting to Python 3.14
827827
implementation details.
828828
(Contributed by Victor Stinner in :gh:`120600` and :gh:`124127`.)
829829

830+
* The :c:func:`PyTuple_SET_ITEM` inline function may not be passed ``NULL``.
831+
This has always been the documented behavior, but was not enforced for
832+
the value until now. :c:var:``Py_None` should be used instead of ``NULL``.
833+
830834

831835
Deprecated
832836
----------

0 commit comments

Comments
 (0)