Repository navigation
chore!: drop support for Python 3.9 - #195
Merged
Merged
Conversation
Python 3.9 is EOL since October 2025. Dropping it also lets the dependency on httpx2 resolve to a current release instead of being pinned back to 2.0.0, the last version supporting 3.9. - requires-python: >=3.9 -> >=3.10 - drop the 3.9 classifier and CI/nox matrix entry - bump ruff target-version to py310 and apply the resulting pyupgrade fixes (Callable from collections.abc, X | None annotations) - refresh pdm.lock: httpx2 2.0.0 -> 2.14.0, httpcore2 2.0.0 -> 2.14.0
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.
What
Raise
requires-pythonfrom>=3.9to>=3.10.Stacked on #194 (httpx2 migration) — merge that first.
Why
Two reasons:
httpx2. chore: migrate from httpx to httpx2 #194 had to pin the lock tohttpx2==2.0.0because that's the last release supporting 3.9; the 3.9 dependency made CI exercise a two-year-stale client. With 3.10 as the floor, the lock resolves tohttpx2==2.14.0/httpcore2==2.14.0— 13 minor releases of fixes that were previously unreachable.Changes
requires-python:>=3.9→>=3.10; drop the3.9classifiernoxfile.py: drop 3.9rufftarget-version:py39→py310, then applied the pyupgrade fixes this now permits:Callableimports fromcollections.abc(auth.py,utils.py)Optional[...]→X | None(MaybeAuthinauth.py)pdm.lock:httpx22.0.0 → 2.14.0,httpcore22.0.0 → 2.14.0. The latter switches fromcertifitotruststore, so default TLS verification now uses the OS trust store.README.md: requirements line said>=3.8— stale since 3.9 was adopted; corrected to>=3.10Breaking
Yes for downstream users on 3.9, hence the
!and anews/*.remove.mdentry is warranted. Flagging rather than deciding: if you'd rather keep 3.9 for a while, close this and #194 can stay pinned tohttpx2==2.0.0.Tests
httpx22.14.0 / 2.16.0 (3.14 has the 2 pre-existingtrustmeskips)ruff check/ruff format --check: cleanmypy: same 9 pre-existing errors asmain, none new