hotdata-framework
A Python framework for building Hotdata integrations.
Shared runtime primitives for Hotdata integrations: workspace semantics, execution context, query state, run history, and replayable result handles. Framework packages (Marimo, Jupyter, Streamlit, LangGraph) depend on this package.
Runtime boundary and guarantees are defined in CONTRACT.md.
Features
- Environment-driven client setup — create clients from
HOTDATA_API_KEY, optionalHOTDATA_API_URL, andHOTDATA_WORKSPACE. - Workspace resolution — choose an explicit workspace from env, otherwise discover workspaces and select the active workspace or first available workspace.
- HTTP resilience — retry SQL execution on stale pooled sockets. Transport-level retries are the SDK's own default, which this package leaves in place so a request is never blindly replayed on a response status. That is a claim about the transport, which cannot know what it would be replaying.
ManagedDatabaseClientretries at the call layer, which can: a managed load is safe to re-send because it carries the sameupload_idand the API replays its receipt for that id rather than applying the load twice. - SQL execution helper — run SQL through
POST /v1/query, poll async query runs when needed, and return aQueryResult. - Result utilities — convert query results to records, pandas DataFrames, or metadata dictionaries for adapter display layers.
- History helpers — list recent results and query run history with normalized dataclasses.
- Managed databases — create Hotdata-owned catalogs, declare tables, upload parquet, and load managed tables (mirrors
hotdata databasesin the CLI). - Indexes — build BM25, vector, or sorted indexes on managed tables, mirroring
hotdata indexes create(managed databases only). Waits on the background build job and surfaces its failure, instead of reporting the phantom success the submit call returns. - Health helpers — build compact API/workspace health summaries for UI integrations.
Install:
uv pip install hotdata-framework
# or: pip install hotdata-framework
Example:
python examples/basic_usage.py
Development (uses uv; creates .venv/ in this repo):
uv sync --locked
uv run pytest
uv.lock is checked in so CI can run uv sync --locked. The default dev group (pytest) is enabled via [tool.uv] default-groups.
Metadata
Release files for hotdata-framework 0.14.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| hotdata_framework-0.14.0.tar.gz | 140.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| hotdata_framework-0.14.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 169.1 kB
Release files / hotdata_framework-0.14.0.tar.gz
| Download URL | hotdata_framework-0.14.0.tar.gz |
|---|---|
| Size | 140.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bc6b675fbf3dfc26b4117410704321cda5c86ff57e32f4085f63706d35e392d1
|
|
BLAKE2b-256 checksum How to use checksums |
3183359e7b4cfdccb31d0ce4028524e2d8df1341f3decbd55a972f4f293db670
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency logRelease files / hotdata_framework-0.14.0-py3-none-any.whl
| Download URL | hotdata_framework-0.14.0-py3-none-any.whl |
|---|---|
| Size | 29.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c2f82b6bcb39af7efece9d154b62d33a353f97d8ac6bec266827d7b4a1c6c672
|
|
BLAKE2b-256 checksum How to use checksums |
56e3e4043e8826d4580a16c147cb624329834a9bd607985278c6a52e6441ac21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 1, 2026.
Transparency log