From 2c3fe5eeb2b64deb2132d9259e74b521c14fd92d Mon Sep 17 00:00:00 2001 From: Petr Viktorin Date: Wed, 8 Jun 2022 17:03:07 +0200 Subject: [PATCH] gh-87961: Remove outdated notes from functions that aren't in the Limited API (GH-93581) * Remove outdated notes from functions that aren't in the Limited API Nowadays everything that *is* in the Limited API has a note added automatically. These notes could mislead people to think that these functions could never be added to the limited API. Remove them. * Also remove forgotten note on tp_vectorcall_offset not being finalized --- Doc/c-api/call.rst | 18 ------------------ Doc/c-api/structures.rst | 2 -- Doc/c-api/typeobj.rst | 6 ------ 3 files changed, 26 deletions(-) diff --git a/Doc/c-api/call.rst b/Doc/c-api/call.rst index cdf72bc1f4714a..13ef8b217a1622 100644 --- a/Doc/c-api/call.rst +++ b/Doc/c-api/call.rst @@ -144,8 +144,6 @@ Vectorcall Support API However, the function ``PyVectorcall_NARGS`` should be used to allow for future extensions. - This function is not part of the :ref:`limited API `. - .. versionadded:: 3.8 .. c:function:: vectorcallfunc PyVectorcall_Function(PyObject *op) @@ -158,8 +156,6 @@ Vectorcall Support API This is mostly useful to check whether or not *op* supports vectorcall, which can be done by checking ``PyVectorcall_Function(op) != NULL``. - This function is not part of the :ref:`limited API `. - .. versionadded:: 3.8 .. c:function:: PyObject* PyVectorcall_Call(PyObject *callable, PyObject *tuple, PyObject *dict) @@ -172,8 +168,6 @@ Vectorcall Support API It does not check the :const:`Py_TPFLAGS_HAVE_VECTORCALL` flag and it does not fall back to ``tp_call``. - This function is not part of the :ref:`limited API `. - .. versionadded:: 3.8 @@ -256,8 +250,6 @@ please see individual documentation for details. Return the result of the call on success, or raise an exception and return *NULL* on failure. - This function is not part of the :ref:`limited API `. - .. versionadded:: 3.9 @@ -343,8 +335,6 @@ please see individual documentation for details. Return the result of the call on success, or raise an exception and return *NULL* on failure. - This function is not part of the :ref:`limited API `. - .. versionadded:: 3.9 @@ -357,8 +347,6 @@ please see individual documentation for details. Return the result of the call on success, or raise an exception and return *NULL* on failure. - This function is not part of the :ref:`limited API `. - .. versionadded:: 3.9 @@ -372,8 +360,6 @@ please see individual documentation for details. Return the result of the call on success, or raise an exception and return *NULL* on failure. - This function is not part of the :ref:`limited API `. - .. versionadded:: 3.9 .. c:function:: PyObject* PyObject_VectorcallDict(PyObject *callable, PyObject *const *args, size_t nargsf, PyObject *kwdict) @@ -388,8 +374,6 @@ please see individual documentation for details. already has a dictionary ready to use for the keyword arguments, but not a tuple for the positional arguments. - This function is not part of the :ref:`limited API `. - .. versionadded:: 3.9 .. c:function:: PyObject* PyObject_VectorcallMethod(PyObject *name, PyObject *const *args, size_t nargsf, PyObject *kwnames) @@ -410,8 +394,6 @@ please see individual documentation for details. Return the result of the call on success, or raise an exception and return *NULL* on failure. - This function is not part of the :ref:`limited API `. - .. versionadded:: 3.9 diff --git a/Doc/c-api/structures.rst b/Doc/c-api/structures.rst index ff5ecf24072c1a..86d4536f8d28e7 100644 --- a/Doc/c-api/structures.rst +++ b/Doc/c-api/structures.rst @@ -321,8 +321,6 @@ There are these calling conventions: or possibly ``NULL`` if there are no keywords. The values of the keyword arguments are stored in the *args* array, after the positional arguments. - This is not part of the :ref:`limited API `. - .. versionadded:: 3.7 diff --git a/Doc/c-api/typeobj.rst b/Doc/c-api/typeobj.rst index df479046d4aeb7..7927e1eb129e99 100644 --- a/Doc/c-api/typeobj.rst +++ b/Doc/c-api/typeobj.rst @@ -727,12 +727,6 @@ and :c:type:`PyType_Type` effectively act as defaults.) When a user sets :attr:`__call__` in Python code, only *tp_call* is updated, likely making it inconsistent with the vectorcall function. - .. note:: - - The semantics of the ``tp_vectorcall_offset`` slot are provisional and - expected to be finalized in Python 3.9. - If you use vectorcall, plan for updating your code for Python 3.9. - .. versionchanged:: 3.8 Before version 3.8, this slot was named ``tp_print``.