8000 Clarify documentation about PyVectorcall_Function by da-woods · Pull Request #107140 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

Clarify documentation about PyVectorcall_Function #107140

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
merged 2 commits into from
Jul 24, 2023
Merged

Clarify documentation about PyVectorcall_Function #107140

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3b9e279
Clarify documentation about PyVectorcall_*
da-woods Jul 23, 2023
68b6c82
revert NARGS and Call
da-woods Jul 24, 2023
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
Prev Previous commit
revert NARGS and Call
  • Loading branch information
@da-woods
da-woods authored Jul 24, 2023
commit 68b6c8211a51a13b248d2173d5d0b4db7372e4d5
4 changes: 2 additions & 2 deletions Doc/c-api/call.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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)

Expand All @@ -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:
Expand Down
0