8000 chore: drop Python 3.10, require 3.11 for the package and the scaffold by burnash · Pull Request #49 · dlt-hub/dlthub-init · GitHub
[go: up one dir, main page]

Skip to content
< 8000 !--$-->

chore: drop Python 3.10, require 3.11 for the package and the scaffold - #49

Merged
burnash merged 1 commit into
develfrom
chore/drop-python-3.10
Nov 6, 2026
Merged

burnash merged 1 commit into
develfrom
chore/drop-python-3.10

Conversation

@burnash
@burnash burnash commented Nov 6, 2026
Copy link
Copy Markdown
Contributor

Why

Python 3.10 reached end of life in October 2026, and dlthub-client 0.28.8 already requires 3.11. With the scaffold still allowing 3.10, the next lock refresh (#48) produced a split resolution: dlthub-client 0.28.7 and pyarrow 25.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 root pyproject.toml and in src/dlthub_init/scaffolds/minimal_workspace/pyproject.toml.
  • Dropped the tomli fallback dependency and its mypy override; tomllib is stdlib on 3.11+. telemetry.py and scripts/sync_workspace_deps.py import it directly.
  • Ruff target-version and mypy python_version moved to 3.11.
  • Capped beaupy>=3.9,<5 so a lock refresh cannot take a major version silently (the last refresh took 3.12 → 4.0.1 under the open constraint).
  • Re-locked both uv.lock files with plain uv lock, no --upgrade. Pinned versions are unchanged: dlt 1.31.0, dlthub 0.30.0, dlthub-client 0.28.7. tomli and exceptiongroup drop out of the root lock; the scaffold lock loses its 3.10-only duplicate entries.
  • CHANGELOG.md: ### Removed entry for 3.10 and a ### Changed entry for the beaupy cap.

How to check it

make ci passes 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 an agent:authored PR or issue is open). The new bump will lock a single dlthub-client 0.28.8 and pyarrow 26.0.1.

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)
@burnash burnash self-assigned this Nov 6, 2026
@burnash
burnash requested a review from anuunchin November 6, 2026 11:55
@anuunchin anuunchin left a comment
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@burnash
burnash merged commit 4dc8e74 into devel Nov 6, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

0