Skip to content

Skip DuckDB parity checks when the extra is not installed - #7

Closed
pavanamthomas wants to merge 1 commit into
mainfrom
github/duckdb-optional-tests-1fc8
Closed

Skip DuckDB parity checks when the extra is not installed#7
pavanamthomas wants to merge 1 commit into
mainfrom
github/duckdb-optional-tests-1fc8

Conversation

@pavanamthomas

@pavanamthomas pavanamthomas commented Aug 28, 2026

Copy link
Copy Markdown
Owner

pip install -e . followed by pytest was failing three tests with install sqlfeat[duckdb]. The point-in-time claim does not need DuckDB: SQLite versus the independent Pandas calculation still runs, and the planted 99999.0 is excluded on that path.

The DuckDB comparisons skip unless the extra is installed. CI still installs .[duckdb] and runs the full set.

Verified locally: two skips without DuckDB, six passing with it, full suite green after .[duckdb].

The README install line uses `.[duckdb]`, and CI does too. A plain
`pip install -e .` was failing three parity tests on ImportError.
SQLite versus Pandas still runs; the DuckDB comparisons skip unless
the extra is there.

Co-authored-by: Dr. Pavanam Thomas <pavanamthomas@users.noreply.github.com>
@pavanamthomas
pavanamthomas marked this pull request as ready for review August 28, 2026 11:51
@pavanamthomas

Copy link
Copy Markdown
Owner Author

Landed on main as a regular commit. Closing this PR.

@pavanamthomas
pavanamthomas deleted the github/duckdb-optional-tests-1fc8 branch August 28, 2026 12:23
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.

1 participant