feat: support Python 3.11–3.14 via modernized deps#110
Draft
zieka wants to merge 1 commit into
Draft
Conversation
Bump the compiled deps to ranges that ship wheels for 3.11 through 3.14: matplotlib>=3.9, pandas>=2.2,<3.0, numpy>=2.1, networkx>=3.2 (plotly loosened too). The old hard pins (pandas==2.0.3, numpy==1.24.4, matplotlib==3.7.1) have no 3.12+ wheels, which is what kept us on 3.11. requires-python stays >=3.11 so the platform's 3.11 runtime is still supported; the lock is a universal resolve across 3.11-3.14. pandas is capped <3.0 to ride the battle-tested 2.x line (pandas 3.0 is a major breaking release); 2.3.3 still has 3.14 wheels, so nothing is lost. On 3.14.5 this resolves to pandas 2.3.3 / numpy 2.4.6 / matplotlib 3.11 / plotly 6.8 / networkx 3.6. Full 90-notebook papermill sweep: - 86/90 pass. - 4 remaining are environmental and Python-version-independent: 3 need the graphviz `dot` system binary (present in the platform image), 1 is recommendations.ipynb (undeclared gradio_client dep). - 0 failures attributable to 3.14 or the modern pandas/numpy APIs. The same modern-dep set also runs on 3.11 (spot-checked), so support is genuinely 3.11-3.14, not a 3.14-only fork. Also add 3.14 to the prerelease workflow's python_version choices so a candidate can be CI-built/tested under 3.14.
zieka
force-pushed
the
feat/python-3.14-compat
branch
from
cf87ff0 to
ee2741f
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
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.
Problem
pandas==2.0.3,numpy==1.24.4,matplotlib==3.7.1have no wheels for 3.12+, so newer Pythons can't install them.Objectives
requires-python>=3.11so the platform's 3.11 runtime still works.Assumptions
code-data-science==2.2.0only needspandas>=2.0.3(no caps), so it doesn't block the bump.pandascapped<3.0on purpose; 2.3.3 still ships 3.14 wheels, avoiding the pandas 3.0 major.Changes
(1)pyproject.toml:matplotlib>=3.9,pandas>=2.2,<3.0,numpy>=2.1,networkx>=3.2,plotly>=5.14.1;uv.lockregenerated.(1,2)README.md: drop the< 3.13ceiling; state 3.11–3.14 supported.requires-python>=3.11unchanged.(3)prerelease.yml: add3.14topython_versionchoices.Notes
dotbinary ×3, undeclaredgradio_client×1), none from 3.14/modern deps. Same set runs on 3.11.2.0.0a2published from this branch; CIuv sync --python 3.14passed on Linux.checks.ymlstill validates only under 3.11; a 3.11–3.14 matrix would exercise resolution (andpoe check-options) per-version in CI.mainon merge.