Skip to content

[3.12] Fix PyVectorcall_Function doc versionadded (GH-107140) #107173

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vstinner merged 1 commit into from
Jul 24, 2023
Merged

[3.12] Fix PyVectorcall_Function doc versionadded (GH-107140) #107173

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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>
  • Loading branch information
@da-woods @miss-islington
da-woods authored and miss-islington committed Jul 24, 2023
commit 1d5e4301bd25dbfc8b49f77746e167405e0bab80
2 changes: 1 addition & 1 deletion Doc/c-api/call.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)

Expand Down