From 3b9e279c8d593bc5e7fba303399a2d614d136503 Mon Sep 17 00:00:00 2001 From: da-woods Date: Sun, 23 Jul 2023 18:51:26 +0100 Subject: [PATCH 1/2] Clarify documentation about PyVectorcall_* 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 --- Doc/c-api/call.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Doc/c-api/call.rst b/Doc/c-api/call.rst index 8be4b5ab80c2de..8d889e66117d66 100644 --- a/Doc/c-api/call.rst +++ b/Doc/c-api/call.rst @@ -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) @@ -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) @@ -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: From 68b6c8211a51a13b248d2173d5d0b4db7372e4d5 Mon Sep 17 00:00:00 2001 From: da-woods Date: Mon, 24 Jul 2023 08:04:12 +0100 Subject: [PATCH 2/2] revert NARGS and Call --- Doc/c-api/call.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Doc/c-api/call.rst b/Doc/c-api/call.rst index 8d889e66117d66..aed4ae44c76eea 100644 --- a/Doc/c-api/call.rst +++ b/Doc/c-api/call.rst @@ -140,7 +140,7 @@ Vectorcall Support API However, the function ``PyVectorcall_NARGS`` should be used to allow for future extensions. - .. versionadded:: 3.9 + .. versionadded:: 3.8 .. c:function:: vectorcallfunc PyVectorcall_Function(PyObject *op) @@ -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.9 + .. versionadded:: 3.8 .. _capi-call: