From: Miss Islington (bot) <31488909+miss-islington@users.noreply.github.com>
Date: Mon, 24 Jul 2023 13:06:46 +0000 (-0700)
Subject: [3.11] Fix PyVectorcall_Function doc versionadded (GH-107140) (#107174)
X-Git-Tag: v3.11.5~151
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=579868e8f1f7995570b2c101b8805e015341f62c;p=thirdparty%2FPython%2Fcpython.git

[3.11] Fix PyVectorcall_Function doc versionadded (GH-107140) (#107174)

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 <dw-git@d-woods.co.uk>
---

diff --git a/Doc/c-api/call.rst b/Doc/c-api/call.rst
index a574965bb126..838af604dca0 100644
--- a/Doc/c-api/call.rst
+++ b/Doc/c-api/call.rst
@@ -156,7 +156,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)