feat!: require Python 3.11#109
Open
zieka wants to merge 1 commit into
Open
Conversation
sjungling
reviewed
Jun 15, 2026
| ] | ||
| license = { text = "Apache-2.0" } | ||
| requires-python = ">=3.9" | ||
| requires-python = ">=3.11" |
Member
There was a problem hiding this comment.
Suggested change
| requires-python = ">=3.11" | |
| requires-python = "=3.11" |
should probably be explicit
Raise the supported Python floor from 3.9 to 3.11 and move CI (checks.yml, publish.yml) to 3.11, regenerating uv.lock on 3.11 (drops <3.11-only backports such as exceptiongroup). This matches the Moderne platform's notebook runtime, whose mod-cli-base image ships CPython 3.11 specifically because pandas==2.0.3 has pre-built wheels for 3.11 but not 3.12+. The original 1.0 attempt to move to 3.12 (#76) was reverted (#83) for this reason; 3.11 is the coordinated, deployable target. Moving to 3.12+ is a separate effort gated on bumping pandas and the platform image moving in lockstep. BREAKING CHANGE: Python 3.9 and 3.10 are no longer supported.
zieka
force-pushed
the
feat/python-3.11-for-2.0.0
branch
from
4249383 to
e5e6d5b
Compare
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
2 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.
What
Raises the supported Python floor from 3.9 → 3.11:
pyproject.toml:requires-python = ">=3.11"checks.yml,publish.yml): Python3.9→3.11(bothsetup-pythonanduv sync --python)uv.lock: regenerated on 3.11 (net −626 lines — drops<3.11-only backports likeexceptiongroup)README.md/CLAUDE.md: doc text updated to 3.11Why 3.11 (and not 3.12)
These notebooks execute inside the Moderne platform's
mod-cli-baseimage, which deliberately ships CPython 3.11 because this package pinspandas==2.0.3, which has pre-built wheels for 3.11 but not 3.12+ (source builds fail on 3.12).pandas(≥2.1) and the platform image moving in lockstep.Validation (local CPython 3.11)
poe check-sentence-casing,poe check-options(the checks CI runs)dependency_tree_view(tree grid),composite_recipe_results_sankey(plotly),cyclomatic_complexity_heatmap(matplotlib)dotsystem binary (present in the platform image; would fail identically on 3.9) — not a 3.11 issueSequencing / release
2.0.0a1from this branch for the platform to smoke-test under real 3.11 before this lands / before cutting2.0.0final.2.0.0version number is stamped by the Publish workflow viasemantic-release version --major; nothing is hardcoded here.BREAKING CHANGE: Python 3.9 and 3.10 are no longer supported.