ci: don't build hypothesis from source - #6411
Merged
Merged
Conversation
Member
Author
bschoenmaeckers
approved these changes
Sep 14, 2026
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.
Split from #6389
It turns out that recent hypothesis releases ship a native component... and that this is a nice problem to have, because it's a Rust (PyO3) component! 🎉
Unfortunately this can break our CI, because we currently end up attempting to build hypothesis from source, and if the PyO3 version used by hypothesis doesn't support the new platform we're testing on the build fails. The simplest thing to do seems to be what we already do for
numpywhere we only run those tests if prebuilt numpy is available.I ran into this testing #6389 locally, however it also applies to future CPython versions and also I think is the likely cause of #6406 being broken.