Skip to content

Support DuckDB 2.0 and Python 3.15, and add a motherduck extra - #235

Merged
leonardovida merged 3 commits into
mainfrom
duckdb-2-support
Nov 17, 2026
Merged

leonardovida merged 3 commits into
mainfrom
duckdb-2-support

Conversation

@leonardovida

Copy link
Copy Markdown
Owner

Summary

Lifts the DuckDB cap now that the dialect handles DuckDB 2.0 results (#230, #232) and Arrow output (#234). Resolves #228.

  • Dependency: 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.
  • motherduck extra: requires duckdb>=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.
  • Python 3.15: classifier, CI and nox.
  • CI: build_backend runs 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 temporary duckdb_2_0 job is removed. The MotherDuck workflow installs the motherduck extra.
  • Docs: a DuckDB 2.0 section in the caveats guide, including the exit-time nanobind: leaked report DuckDB 2.0 can print.

No version bump here. The release follows in its own PR.

Tests

Full suite locally:

Python DuckDB SQLAlchemy Result
3.11 1.5.6 2.0.52 933 passed, 10 skipped
3.13 2.0.0 2.1.9 933 passed, 10 skipped
3.12 2.0.0 2.0.58 933 passed, 10 skipped
3.12 2.0.0 2.0.0 930 passed, 13 skipped
3.15 2.0.0 2.0.45 933 passed, 10 skipped
3.10 1.3.0 2.0.0 926 passed, 17 skipped

Built wheel, installed with --only-binary :all::

  • Python 3.13 resolves DuckDB 2.0.0 and passes scripts/verify_distribution.py, with and without pyarrow and pandas
  • Python 3.13 with [motherduck] resolves DuckDB 1.5.6
  • Python 3.10 resolves DuckDB 1.5.6
  • Python 3.15 resolves DuckDB 2.0.0 and passes scripts/verify_distribution.py

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.
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-17T19:40:24.653726Z fca4ce1 PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot 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.

💡 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".

Comment thread uv.lock
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" },

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge 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 👍 / 👎.

@leonardovida
leonardovida merged commit fb572ae into main Nov 17, 2026
46 checks passed
@leonardovida
leonardovida deleted the duckdb-2-support branch November 17, 2026 21:02
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.

duckdb<2 silently downgrades DuckDB across a major version in downstream resolvers

1 participant