1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
[project]
name = "sql-cli-tests"
version = "0.1.0"
description = "Test suite for sql-cli SQL engine"
requires-python = ">=3.10"
dependencies = [
"pandas>=2.0.0",
"numpy>=1.24.0",
"pytest>=7.0.0",
"pytest-cov>=4.0.0",
"flask>=2.0.0",
]
[tool.pytest.ini_options]
testpaths = ["tests"]
python_files = "test_*.py"
python_classes = "Test*"
python_functions = "test_*"
[tool.ruff]
line-length = 120
target-version = "py310"
[tool.hatch.build.targets.wheel]
packages = ["tests"]
[build-system]
requires = ["hatchling"]
build-backend = "hatchling.build"
[dependency-groups]
test = [
# Pinned, not floating. The parity corpus contains cases where the SQL
# standard leaves behaviour implementation-defined (see "Where the standard
# leaves a choice open" in docs/SQL_PARITY.md) — P17 NULL ordering and P24
# frame defaults among them. Those cases encode whatever DuckDB currently
# chooses, so an unpinned bump can redden the gate for reasons that have
# nothing to do with our engine, and point at the wrong place when it does.
# Bump deliberately: raise this, run the harness, review any drift.
"duckdb==1.5.5",
]