Files
zeekay 1b367e2b62 chore: rebase the tree onto upstream master
The tree was a debranded snapshot of upstream taken around 2026-02-20, and
upstream has moved about five months since. This replaces it with upstream
master, mechanically re-derived: bin/debrand does the rename, and the
pipeline and squashed migrations are restored from the shipped tree.

Not a merge. The previous import replaced the tree wholesale in a single
commit, so there is no shared content history to merge against. Reproducing
the rename on the new tree is what actually converges.

What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints,
compose files, LLM.md, and insights/migrations. The squashed initial
migration is load-bearing — the live database records it by name, so
upstream's ~918 individual migrations cannot come back.

Nine products are dropped as unreferenced. Twenty-one more that we do not run
are kept anyway because the core app still imports them; unpicking those is a
refactor and does not belong in a rebase.

This base does not build yet, and the reasons are not in the rename:
upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against
our 4.2, and the dependency manifests still name upstream packages that we
republish under our own names. Those are decisions, not renames.
2026-08-01 15:44:40 -07:00

42 lines
1.7 KiB
TOML

[package]
name = "deltalite-python"
# Mirrors pyproject.toml in this directory (always identical); bump both together.
version = "0.1.3"
edition = "2021"
# CI compiles with this exact toolchain; cargo's MSRV-aware resolver uses it to
# avoid picking dependency versions CI cannot build (aws-* crates move MSRV often).
rust-version = "1.91.1"
publish = false
[lib]
name = "deltalite_python"
# `cdylib` for the Python wheel that maturin builds; `rlib` so other Rust crates could
# depend on the binding layer if useful later -- `cdylib` alone would break that. Same
# shape as `rust/insightsql/parser`.
#
# NOTE: keep Rust unit tests OUT of this crate. `extension-module` (below) suppresses
# the libpython link, so a `cargo test` harness binary for this crate cannot link on
# Linux. All Rust tests live in `deltalite-core`, which has no pyo3 dependency.
crate-type = ["cdylib", "rlib"]
[lints]
workspace = true
[dependencies]
deltalite-core = { path = "../core" }
# `abi3-py312` matches the repo convention (`rust/insightsql/parser`): one wheel works on
# every Python 3.12+ via the stable CPython ABI, including the pinned prod 3.13.
#
# pyo3 0.28 is dictated by arrow 58's `pyarrow` feature (arrow major fixed by
# `deltalake` 0.32). Cargo allows one pyo3 version per workspace (`links = "python"`),
# so this must stay in lockstep with `rust/insightsql/parser`.
pyo3 = { version = "0.28", features = ["extension-module", "abi3-py312"] }
arrow = { version = "58", features = ["pyarrow"] }
arrow-array = { version = "58" }
arrow-schema = { version = "58" }
deltalake = { version = "=0.32.4", default-features = false, features = ["s3", "rustls"] }
serde_json = { workspace = true }
tokio = { workspace = true }