From 4fd576478c99b999feac68b71f317fd9d320662f Mon Sep 17 00:00:00 2001 From: "Miss Islington (bot)" <31488909+miss-islington@users.noreply.github.com> Date: Mon, 24 Jul 2023 06:06:16 -0700 Subject: [3.12] Fix PyVectorcall_Function doc versionadded (GH-107140) (#107173) Fix PyVectorcall_Function doc versionadded (GH-107140) The documentation implies that PyVectorcall_Function() was available in Python 3.8. This is half-true - it was available under a different name. I think it's clearer to set the "version added" to 3.9. (cherry picked from commit 0a9b339363a59be1249189c767ed6f46fd71e1c7) Co-authored-by: da-woods --- Doc/c-api/call.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/c-api/call.rst b/Doc/c-api/call.rst index 143fce3..f4e4014 100644 --- a/Doc/c-api/call.rst +++ b/Doc/c-api/call.rst @@ -165,7 +165,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) -- cgit v0.12