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

pypy/graalpy: set Py_LIMITED_API when abi3 requested #4237

Merged
merged 2 commits into from
Jun 10, 2024

Conversation

davidhewitt
Copy link
Member

Inspired by the CI failure attempting to merge #4194

This PR changes the abi3 builds on PyPy and GraalPy so that if the abi3 feature is set they will still set the Py_LIMITED_API config.

Technically speaking this is a bit pointless because neither PyPy nor GraalPy support the abi3 stable ABI, but it makes it easier for us to reason about feature combinations because this way when the abi3 feature is set we always build PyO3 to only use the limited API.

I think these same changes would also make sense with #2865 because then the base cfg of the limited API would be the exact same code regardless of what interpreter implementation we're running on.

Copy link
Contributor

@LilyFoote LilyFoote left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks reasonable to me.

@davidhewitt davidhewitt added this pull request to the merge queue Jun 10, 2024
Merged via the queue into PyO3:main with commit f66124a Jun 10, 2024
80 of 81 checks passed
@davidhewitt davidhewitt deleted the pypy-limited-api branch June 10, 2024 08:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants