millpond/pyproject.toml at main · PostHog/millpond · GitHub

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
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
[build-system]
requires = ["hatchling", "hatch-vcs"]
build-backend = "hatchling.build"

[tool.hatch.version]
source = "vcs"

[tool.hatch.build.hooks.vcs]
version-file = "millpond/_version.py"

[project]
name = "millpond"
dynamic = ["version"]
description = "Kafka to DuckLake"
license = {file = "LICENSE"}
requires-python = ">=3.12"
dependencies = [
    "confluent-kafka>=2.6",
    # Pinned exactly. 1.5.2 is the DuckDB release that ships DuckLake 1.0,
    # the breaking-change rev of the ducklake extension that millpond/ducklake.py
    # has been aligned against. The DuckLake 1.x line is pre-stable, and the
    # extension repository does not expose installable version specifiers for
    # ducklake — INSTALL ducklake VERSION '...' returns 404. To compensate,
    # tests/unit/test_ducklake_pin.py asserts the build SHA of the loaded
    # extension as a drift canary. Bumping this DuckDB pin (or letting the
    # extension SHA move) requires updating that canary explicitly.
    "duckdb==1.5.2",
    "pyarrow>=18.0",
    "orjson>=3.10",
    "prometheus-client>=0.21",
    # Required by duckdb's Python conversion for TIMESTAMPTZ columns; the
    # stdlib zoneinfo module isn't accepted as a substitute as of 1.4.x.
    "pytz>=2024.1",
    "pyyaml>=6.0.3",
    # OpenTelemetry SDK + HTTP OTLP log exporter. Ships structured logs
    # to PostHog Logs when POSTHOG_PROJECT_TOKEN is set. PostHog
    # terminates standard OTLP/HTTP at /i/v1/logs — no PostHog-specific
    # Python package exists.
    "opentelemetry-sdk>=1.30",
    "opentelemetry-exporter-otlp-proto-http>=1.30",
    # 1.42 deprecated opentelemetry.sdk._logs.LoggingHandler in favor of the
    # one shipped from opentelemetry-instrumentation-logging. Same API,
    # same wire behavior, just no DeprecationWarning at construction.
    # Ceiling is to bound surprise — the instrumentation contrib packages
    # have moved module paths across minor revs before (the handler lives
    # at opentelemetry.instrumentation.logging.handler today; that's NOT
    # the package's documented public surface — public is
    # LoggingInstrumentor — so a future rev could move it without a
    # deprecation cycle. Bump deliberately.
    "opentelemetry-instrumentation-logging>=0.50b0,<0.64",
]

[project.optional-dependencies]
msk-iam = ["aws-msk-iam-sasl-signer-python>=1.0.0"]

[project.scripts]
millpond = "millpond.main:main"

[dependency-groups]
dev = [
    "pytest>=9.0.3",
    "ruff>=0.8",
    "testcontainers>=4.14.2",
]

[tool.ruff]
target-version = "py312"
line-length = 120

[tool.ruff.lint]
select = ["E", "F", "I", "UP"]

[tool.pytest.ini_options]
markers = [
    "integration: marks tests as integration tests (deselect with '-m \"not integration\"')",
    "e2e: marks tests as E2E tests requiring docker-compose stack",
]
pythonpath = ["tools"]
testpaths = ["tests"]
# Keep collection scoped to `tests/` only — local working clones (e.g.
# an untracked `lakekeeper/` source tree) carry their own tests/ whose
# deps we don't install.
norecursedirs = ["lakekeeper", ".venv", "node_modules"]

[tool.uv]
exclude-newer = "7 days"
constraint-dependencies = [
    "pygments>=2.20.0",
    "requests>=2.33.0",
]