Use PyPy 3.11 in CI#4146
Open
marko1olo wants to merge 1 commit into
Open
Conversation
marko1olo
force-pushed
the
fix-pypy39-hatch-cryptography
branch
from
727fa1a to
5198868
Compare
marko1olo
changed the title
Author
|
Follow-up from the first run on the updated branch: the PyPy 3.11 bootstrap now gets past dependency installation successfully. The remaining test failures I checked are the existing |
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.
The current PyPy 3.9 CI jobs can fail before MkDocs tests start while installing Hatch.
Two separate bootstrap issues show up with the old PyPy target:
cryptographyno longer publishes PyPy 3.9 wheels, so pip falls back to a source build that now requires PyPy 3.11 through PyO3zstandarddependency has no PyPy wheel for the old interpreter and the source build fails while looking fordistutils.msvc9compilerMkDocs already tests CPython 3.8 and 3.9 directly. Updating the PyPy leg to PyPy 3.11 keeps PyPy implementation coverage while using currently supported wheels for the CI bootstrap dependencies.
Local checks:
git diff --checkpython -m pip install --dry-run --upgrade hatchcryptographyandbackports-zstdresolve PyPy 3.11 wheels formanylinux_2_28_x86_64,win_amd64, andmacosx_11_0_arm64