chore: remove stale ciwheelbuild config for PyPy#2975
Merged
kevinjqliu merged 1 commit intoapache:mainfrom Jan 28, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale for this change
I noticed our nightly builds kept showing these annotations:
We haven't shipped a PyPy build since 0.9.1 (https://pypi.org/project/pyiceberg/0.9.1/#files), so this skip rule isn't doing anything anymore. Removed it to clean up the warnings.
PyPy wheels are no longer built by default following the cibuildwheel 3.0 release and it was bumped in #2099. If we want PyPy support back, we can re-add the builds instead of just skipping tests.
Are these changes tested?
Successful run on personal branch: https://github.com/geruh/iceberg-python/actions/runs/21427296271
Are there any user-facing changes?
No