Repository navigation
Support DuckDB 2.0 and Python 3.15, and add a motherduck extra - #235
Conversation
Lift the DuckDB requirement to <3, test DuckDB 1.x and 2.x across the CI matrices and nox, add Python 3.15, and add a motherduck extra that pins the DuckDB range MotherDuck accepts.
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fca4ce1e12
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| requires-dist = [ | ||
| { name = "alembic", marker = "extra == 'dev'", specifier = ">=1.13,<2" }, | ||
| { name = "duckdb", specifier = ">=1.3.0,<2" }, | ||
| { name = "duckdb", specifier = ">=1.3.0,<3" }, |
There was a problem hiding this comment.
Regenerate the lock for DuckDB 2 on Python 3.15
Although the metadata range now permits DuckDB 2, the committed lock still contains only duckdb==1.5.6, whose wheel list ends at CPython 3.14. Consequently, a Python 3.15 developer using uv sync is directed to the 1.5.6 source distribution instead of the supported 2.0 wheel, contradicting the new nox matrix that skips all 1.x versions on 3.15 because they have no wheels. Upgrade DuckDB while regenerating the lock so it records Python-specific 1.x/2.x resolutions.
Useful? React with 👍 / 👎.
Summary
Lifts the DuckDB cap now that the dialect handles DuckDB 2.0 results (#230, #232) and Arrow output (#234). Resolves #228.
duckdb>=1.3.0,<3. DuckDB 2.x requires Python 3.11, so Python 3.10 keeps DuckDB 1.x. DuckDB 1.x has no Python 3.15 wheels, so Python 3.15 uses DuckDB 2.x.motherduckextra: requiresduckdb>=1.4.1,<2, the range MotherDuck accepts. MotherDuck rejects DuckDB 2.x clients with an error that asks for a downgrade, and a plain install on Python 3.11+ now resolves DuckDB 2.x. README, the getting started guide and the MotherDuck guide point MotherDuck users at the extra.nox.build_backendruns DuckDB 1.x on Python 3.10 to 3.14 and DuckDB 2.x on Python 3.11 to 3.15. The SQLAlchemy 2.0, platform and upstream-suite jobs run both DuckDB lines. The temporaryduckdb_2_0job is removed. The MotherDuck workflow installs themotherduckextra.nanobind: leakedreport DuckDB 2.0 can print.No version bump here. The release follows in its own PR.
Tests
Full suite locally:
Built wheel, installed with
--only-binary :all::scripts/verify_distribution.py, with and without pyarrow and pandas[motherduck]resolves DuckDB 1.5.6scripts/verify_distribution.py