Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 579868e

Browse filesBrowse files
miss-islingtonda-woods
miss-islington
and
da-woods
authored
[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 0a9b339) Co-authored-by: da-woods <dw-git@d-woods.co.uk>
1 parent 798d83b commit 579868e
Copy full SHA for 579868e

File tree

Expand file treeCollapse file tree

1 file changed

+1
-1
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+1
-1
lines changed

‎Doc/c-api/call.rst

Copy file name to clipboardExpand all lines: Doc/c-api/call.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -156,7 +156,7 @@ Vectorcall Support API
156156
This is mostly useful to check whether or not *op* supports vectorcall,
157157
which can be done by checking ``PyVectorcall_Function(op) != NULL``.
158158
159-
.. versionadded:: 3.8
159+
.. versionadded:: 3.9
160160
161161
.. c:function:: PyObject* PyVectorcall_Call(PyObject *callable, PyObject *tuple, PyObject *dict)
162162

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.