Add CI for PyPy3.9 and PyPy3.10 #316
Merged
Conversation
This file contains 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
|
Nice! Looking good. Looking forward to stripping those suffixes. |
|
Thanks! 🙌 (And thanks for the patience. Didn't get a notification that this was no longer draft.) |
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.
I have identified the cause of the erroneous CLI output from #314.
It was due to a rogue print statement that affects PyPy 3.9-v7.3.13 and PyPy 3.10-v7.3.13. This was fixed in v7.3.14.
GitHub Action's cached PyPy versions are still on v7.3.13 as of today because v7.3.14 is just 2 weeks old. This PR will be updated to remove the
-v7.3.14suffixes once the upstream cached versions are updated.PyPy 3.8 is no longer supported upstream as of today.