Skip to content
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

FFI for PEP 590 Vectorcall #641

Merged
merged 1 commit into from
Oct 24, 2019
Merged

FFI for PEP 590 Vectorcall #641

merged 1 commit into from
Oct 24, 2019

Conversation

ijl
Copy link
Contributor

@ijl ijl commented Oct 23, 2019

https://www.python.org/dev/peps/pep-0590/

This was tested on 3.7 using _PyCFunctionFast and 3.8
using PyObject_Vectorcall. Extending pyo3-derive-backend
to generate code using vectorcall is not done here.

This exposes PyObject_Vectorcall with a link_name to the
underscored name on 3.8 because it is expected to be stabilized
on 3.9.

This fixes the "fast" objects being new in 3.7, not 3.6.

https://www.python.org/dev/peps/pep-0590/

This was tested on 3.7 using _PyCFunctionFast and 3.8
using PyObject_Vectorcall. Extending pyo3-derive-backend
to generate code using vectorcall is not done here.

This exposes PyObject_Vectorcall with a link_name to the
underscored name on 3.8 because it is expected to be stabilized
on 3.9.

This fixes the "fast" objects being new in 3.7, not 3.6.
@kngwyu
Copy link
Member

kngwyu commented Oct 24, 2019

Thanks!
Vectorcall looks really nice and I want to use it in PyO3 internally in the future.

@kngwyu kngwyu merged commit 34843d7 into PyO3:master Oct 24, 2019
@kngwyu kngwyu mentioned this pull request Dec 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants