-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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.
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
bpo-42171: Add PEP573-related items to the limited API #23009
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since PEP 590 has been approved, is there still a reason to exclude METH_FASTCALL from the limited C API? The limited C API is supposed to hide implementation details. Do we still consider that "fastcall" and "vectorcall" are implementation details?
Why not adding METH_FASTCALL to the limited C API, rather than adding a new METH_METHOD_ARGS_KWD macro?
OK! If you're fine adding |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks.
@markshannon wrote that "FASTCALL" is a bad name, since there will be faster calling conventions tomorow, but the ship has sailed. Cython uses METH_FASTCALL. It's too late to change it.
When I added METH_FASTCALL, I tried to keep it secret, but Cython started to use the private C API, and here we are :-)
I wouldn't worry that we can't come up with faster-sounding names. Like VictorCall, but that's already taken :) |
METH_VICTORCALL sounds like a good name :-D |
|
The |
That build first failed ( |
https://bugs.python.org/issue42171
Automerge-Triggered-By: GH:encukou