Skip to content

Commit

Permalink
Clarify documentation about PyVectorcall_*
Browse files Browse the repository at this point in the history
The documentation implies that PyVectorcall_NARGS, PyVectorcall_Function, and PyVectorcall_Call were available in Python 3.8.

This is half-true - they were available under a different name. I think it's clearer to set the "version added" to 3.9
  • Loading branch information
da-woods authored Jul 23, 2023
1 parent 956b3de commit 3b9e279
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions Doc/c-api/call.rst
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@ Vectorcall Support API
However, the function ``PyVectorcall_NARGS`` should be used to allow
for future extensions.
.. versionadded:: 3.8
.. versionadded:: 3.9
.. c:function:: vectorcallfunc PyVectorcall_Function(PyObject *op)
Expand All @@ -152,7 +152,7 @@ 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``.
.. versionadded:: 3.8
.. versionadded:: 3.9
.. c:function:: PyObject* PyVectorcall_Call(PyObject *callable, PyObject *tuple, PyObject *dict)
Expand All @@ -164,7 +164,7 @@ Vectorcall Support API
It does not check the :c:macro:`Py_TPFLAGS_HAVE_VECTORCALL` flag
and it does not fall back to ``tp_call``.
.. versionadded:: 3.8
.. versionadded:: 3.9
.. _capi-call:
Expand Down

0 comments on commit 3b9e279

Please sign in to comment.