Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity

gh-87961: Remove outdated notes from functions that aren't in the Limited API (GH-93581) (GH-93604) 

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.

(cherry picked from commit 2c3fe5eeb2)

Co-authored-by: Petr Viktorin <encukou@gmail.com>
This commit is contained in:
Miss Islington (bot) 2022-06-10 07:04:23 -07:00 committed by GitHub
parent c3045d809c
commit 25444124e3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 0 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
Doc/c-api/call.rst
View File

@ -144,8 +144,6 @@ Vectorcall Support API
However, the function ``PyVectorcall_NARGS`` should be used to allow However, the function ``PyVectorcall_NARGS`` should be used to allow
for future extensions. for future extensions.
This function is not part of the :ref:`limited API <stable>`.
.. versionadded:: 3.8 .. versionadded:: 3.8
.. c:function:: vectorcallfunc PyVectorcall_Function(PyObject *op) .. 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, This is mostly useful to check whether or not *op* supports vectorcall,
which can be done by checking ``PyVectorcall_Function(op) != NULL``. which can be done by checking ``PyVectorcall_Function(op) != NULL``.
This function is not part of the :ref:`limited API <stable>`.
.. versionadded:: 3.8 .. versionadded:: 3.8
.. c:function:: PyObject* PyVectorcall_Call(PyObject *callable, PyObject *tuple, PyObject *dict) .. 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 It does not check the :const:`Py_TPFLAGS_HAVE_VECTORCALL` flag
and it does not fall back to ``tp_call``. and it does not fall back to ``tp_call``.
This function is not part of the :ref:`limited API <stable>`.
.. versionadded:: 3.8 .. 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 Return the result of the call on success, or raise an exception and return
*NULL* on failure. *NULL* on failure.
This function is not part of the :ref:`limited API <stable>`.
.. versionadded:: 3.9 .. 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 Return the result of the call on success, or raise an exception and return
*NULL* on failure. *NULL* on failure.
This function is not part of the :ref:`limited API <stable>`.
.. versionadded:: 3.9 .. 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 Return the result of the call on success, or raise an exception and return
*NULL* on failure. *NULL* on failure.
This function is not part of the :ref:`limited API <stable>`.
.. versionadded:: 3.9 .. 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 Return the result of the call on success, or raise an exception and return
*NULL* on failure. *NULL* on failure.
This function is not part of the :ref:`limited API <stable>`.
.. versionadded:: 3.9 .. versionadded:: 3.9
.. c:function:: PyObject* PyObject_VectorcallDict(PyObject *callable, PyObject *const *args, size_t nargsf, PyObject *kwdict) .. 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, already has a dictionary ready to use for the keyword arguments,
but not a tuple for the positional arguments. but not a tuple for the positional arguments.
This function is not part of the :ref:`limited API <stable>`.
.. versionadded:: 3.9 .. versionadded:: 3.9
.. c:function:: PyObject* PyObject_VectorcallMethod(PyObject *name, PyObject *const *args, size_t nargsf, PyObject *kwnames) .. 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 Return the result of the call on success, or raise an exception and return
*NULL* on failure. *NULL* on failure.
This function is not part of the :ref:`limited API <stable>`.
.. versionadded:: 3.9 .. versionadded:: 3.9

2
Doc/c-api/structures.rst
View File

@ -321,8 +321,6 @@ There are these calling conventions:
or possibly ``NULL`` if there are no keywords. The values of the keyword or possibly ``NULL`` if there are no keywords. The values of the keyword
arguments are stored in the *args* array, after the positional arguments. arguments are stored in the *args* array, after the positional arguments.
This is not part of the :ref:`limited API <stable>`.
.. versionadded:: 3.7 .. versionadded:: 3.7

6
Doc/c-api/typeobj.rst
View File

@ -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, When a user sets :attr:`__call__` in Python code, only *tp_call* is updated,
likely making it inconsistent with the vectorcall function. 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 .. versionchanged:: 3.8
Before version 3.8, this slot was named ``tp_print``. Before version 3.8, this slot was named ``tp_print``.