build: drop support for Python 3.9 - #913
Open
qianzhu18 wants to merge 1 commit into
Open
Conversation
Python 3.9 is EOL, and the 0.43.0 RC1 release vote surfaced that the [cli]/[learn]/[start] extras were already broken on it (PEP 604 unions in burr/cli/__main__.py), forcing the release-validation smoke matrix to skip 3.9. Make the floor official everywhere: - pyproject.toml: requires-python >=3.10 - CI: remove 3.9 from the python-package.yml matrices and the now- obsolete 3.9 skip comment in release-validation.yml - docs: README, getting_started/install, contributing/setup, and the website downloads page now state the 3.10+ requirement - scripts/README.md and the shutil-filter comment in scripts/apache_release.py No runtime behavior changes. Fixes apache#900
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
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.
Changes
Python 3.9 is EOL, and the 0.43.0 RC1 release vote surfaced that the
[cli]/[learn]/[start]extras were already broken on it (PEP 604 unions inburr/cli/__main__.py), forcing the release-validation smoke matrix to skip 3.9. This makes the 3.10 floor official everywhere:pyproject.toml:requires-python = ">=3.10"(no version-specific classifiers existed, so nothing else to drop there)3.9from the four Python version matrices in.github/workflows/python-package.yml, and remove the now-obsolete 3.9 skip comment in.github/workflows/release-validation.ymldocs/getting_started/install.rst,docs/contributing/setup.rst, and the website downloads page now state the 3.10+ requirement (the old "core remains compatible with 3.9" notes added by Bump to 0.43.0 #902 are superseded)scripts/README.mdprerequisite and the shutil-filter compatibility comment inscripts/apache_release.py(3.9-3.11 → 3.10-3.11)No runtime behavior changes — metadata, CI, and documentation only.
Fixes #900
How I tested this
uv syncanduv buildsucceed with the newrequires-python— sdist and wheel metadata build cleanlypytest tests/core/test_action.py tests/core/test_application.py tests/test_release_config.py: 235 passed / 61 failed — identical failure set on unmodifiedmainunder the same local interpreter (Python 3.14, above the supported ceiling), so the failures are pre-existing environment effects, not regressionsgrep -rn "3\.9"across toml/yml/rst/md/py confirms no remaining reference to 3.9 as a supported target (the remaining matches are either the historical 0.43.0 release note orlangfuse>=3.9package-version comparisons, both intentionally untouched)Notes
py<3.9AST comments inburr/core/action.py— they predate this change (they are already below the old 3.9 floor) and are harmless permissive parsingscripts/apache_release.py/pyproject.tomlwith the open fix(release): address 0.43.0 RC feedback #882; happy to pick it up after that landsChecklist