MNT: use pypy 3.11 nightly which has a fix for ctypeslib #29051
Merged
+1
−1
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
|
Any idea what the timeline for the next PyPy release is? We have a 2-3 weeks before 2.3.0 goes out. |
|
OK, let's put this in to test the fix. It is easier to track than disabling the test. Thanks Matti. |
No. Definitely not in the next month |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Alternative to #29014. Fixes flaky ctypeslib test on PyPy. There are disadvantages to using PyPy's nightly build: it might cause spurious CI failures when the build is not available (it is not cached by the setup-python action, obviously), or the nightly is unusable. Both those should happen rarely but YMMV. I am tracking PyPy HEAD + Numpy HEAD on ubuntu, macos, windows in a weekly cron-driven CI job here, the ubuntu one is generally green.