Repository navigation
<
8000
!--$-->
chore: drop Python 3.10, require 3.11 for the package and the scaffold - #49
Merged
Merged
Conversation
Python 3.10 reached end of life in October 2026 and dlthub-client 0.28.8 already requires 3.11, so a scaffold that still allowed 3.10 would lock a split resolution (0.28.7 for 3.10, 0.28.8 for 3.11+). The scaffold pins 3.13 via .python-version, so nobody ran it on 3.10 anyway. - requires-python >=3.11 in the root and scaffold pyproject - drop the tomli fallback (tomllib is stdlib on 3.11+) and its mypy override - ruff target and mypy python_version to 3.11 - cap beaupy <5 so a lock refresh cannot take a major silently - re-lock both uv.lock files with plain `uv lock` (no upgrades: dlt stays 1.31.0, dlthub 0.30.0, dlthub-client 0.28.7; tomli and exceptiongroup drop out)
5 tasks
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.
Why
Python 3.10 reached end of life in October 2026, and
dlthub-client0.28.8 already requires 3.11. With the scaffold still allowing 3.10, the next lock refresh (#48) produced a split resolution:dlthub-client0.28.7 andpyarrow25.0.1 for 3.10, the new versions for 3.11+. The scaffold pins 3.13 via.python-version, so nobody ran it on 3.10 anyway.What changed
requires-python = ">=3.11"in the rootpyproject.tomland insrc/dlthub_init/scaffolds/minimal_workspace/pyproject.toml.tomlifallback dependency and its mypy override;tomllibis stdlib on 3.11+.telemetry.pyandscripts/sync_workspace_deps.pyimport it directly.target-versionand mypypython_versionmoved to 3.11.beaupy>=3.9,<5so a lock refresh cannot take a major version silently (the last refresh took 3.12 → 4.0.1 under the open constraint).uv.lockfiles with plainuv lock, no--upgrade. Pinned versions are unchanged: dlt 1.31.0, dlthub 0.30.0, dlthub-client 0.28.7.tomliandexceptiongroupdrop out of the root lock; the scaffold lock loses its 3.10-only duplicate entries.CHANGELOG.md:### Removedentry for 3.10 and a### Changedentry for the beaupy cap.How to check it
make cipasses locally: lint, 132 unit tests, 2 integration tests, both lock guards, the scaffold deps guard, the skills guard and the wheel build.Follow-up
Once this lands, re-run
bump-dlthub-init.yml(close #48 and #47 first, the workflow skips while anagent:authoredPR or issue is open). The new bump will lock a singledlthub-client0.28.8 andpyarrow26.0.1.