feat: remove GraalPy 3.11 (gp311) support#2895
Merged
Merged
Conversation
Drops the GraalPy 3.11 / GraalPy 24.2 builds (gp311_242) as agreed in pypa#2741: a ~6-month overlap after the GraalPy 25 (gp312) release. GraalPy 3.12 (gp312_250) stays. This also removes the GraalPy 24-only workarounds that were explicitly marked "Remove when GraalPy 24.x is dropped": - the Visual Studio compiler-discovery (vswhere) and build-isolation (graalpython#491) workarounds in the Windows backend - the issue-491 Windows skip/filter hacks in test_pep518 and test_dependency_versions (added in the original GraalPy PR pypa#1538 and unneeded since GraalPy 25 per pypa#2597) The uv-doesn't-support-graalpy skip (pypa#2754), the `graalpy` enable group, and the generated constraints pins apply to all GraalPy and are kept. Assisted-by: ClaudeCode:claude-opus-4.8
agriyakhetarpal
approved these changes
Jun 5, 2026
timfel
approved these changes
Jun 7, 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
4 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.
GraalPy 3.11 interacts poorly with delvewheel on Windows. I've seen two errors, #2883, and
ImportError: cannot load C:\Users\runneradmin\AppData\Local\Temp\cibw-run-dwn70_yl\gp311_242-win_amd64\venv-test\Lib\site-packages\python_example.graalpy242-311-native-x86_64-win32.pyd. AFAICT, both work fine in GraalPy 3.12. In #2741 (comment), @timfel said we could drop 3.11 in March. This is after March, so I think the best path forward is to just drop it before 4.0.0 instead of complicating the default windows repair option. Though we could introducegraalpy-eolinstead if better.This gets rid of several workarounds, too.
🤖 AI text below 🤖
Removes GraalPy 3.11 / GraalPy 24.2 (
gp311_242) support, as agreed in #2741 — a ~6-month overlap after the GraalPy 25 (gp312) release. GraalPy 3.12 (gp312_250) stays.What's removed
gp311_242-*entries frombuild-platforms.toml(linux x86_64/aarch64, macOS x86_64/arm64, win_amd64).vswhere) block and the build-isolation (-n) workaround for venv created from virtualenv seeded graalpy does not work on Windows oracle/graalpython#491 in the Windows backend;test_pep518andtest_dependency_versions(added in the original GraalPy PR Support GraalPy #1538 and unneeded since GraalPy 25, per Add GraalPy 25 and remove workarounds for that version. #2597).GraalPy 3.11 v24.2rows in the README anddocs/options.mdsupport tables, plus the matching test fixtures/IDs.Intentionally kept (apply to all GraalPy, not gp311-specific)
uv-doesn't-support-graalpy skip intest/conftest.py(tracked by GraalPy wheel build fails when using uv in build frontend on Windows #2754);graalpyenable group;constraints-python31{1,2}.txtpip-on-Windows pins.Testing
prek -aclean; all 790 unit tests pass.cc @timfel — this is the gp311 drop we discussed in #2741.