Use PyPy 3.11 in CI#4121
Closed
Sean-Kenneth-Doherty wants to merge 2 commits into
Closed
Conversation
Author
|
Closing this draft as a duplicate of #4120. The ready PR carries the same PyPy 3.11 CI fix and the follow-up fixture dedent, with validation and green checks collected there. |
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
1 participant
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.
Summary
draft_docsuser-guide fixture so the PyPy 3.11 test matrix reads the intended pathspec patterns.Why
The current PyPy 3.9 jobs fail before tests run while installing the latest Hatch-compatible dependency set:
cryptographybuilds now require a newer PyPy through PyO3, and the Windows job also trips over azstandardsource build. PyPy 3.11 can install current Hatch cleanly and keeps the matrix covering PyPy without pinning stale bootstrap dependencies.Validation
git diff --check origin/master...HEAD.github/workflows/ci.ymland asserted the matrix containspypy-3.11and no longer containspypy-3.9-v7.x.env TMPDIR=/home/sean/.cache PATH="/home/sean/.cache/mkdocs-pypy-path:/home/sean/.local/share/uv/python/pypy-3.11.15-linux-x86_64-gnu/bin:$PATH" uvx --from hatch --with pip hatch run +py=pypy3 test:testpassed both matrix legs: 725 tests, 4 skipped fortest.pypy3-default; 725 tests, 4 skipped fortest.pypy3-min-req.