heliosdb-nano (Python)
In-process Python binding for HeliosDB-Nano's
embedded database. Calls the Rust EmbeddedDatabase API directly — no subprocess,
no wire protocol, no serialization hop — so Python sees the same path behind the
"embedded beats SQLite" numbers.
import heliosdb_nano
db = heliosdb_nano.EmbeddedDatabase("/path/to/data") # or .in_memory()
db.execute("CREATE TABLE messages (id INT, session_id TEXT, body TEXT)")
db.execute_many(
"INSERT INTO messages (id, session_id, body) VALUES ($1, $2, $3)",
[(1, "s1", "hi"), (2, "s1", "yo"), (3, "s2", "hey")],
)
db.query("SELECT COUNT(DISTINCT session_id) AS n FROM messages") # [{'n': 2}]
db.query("SELECT * FROM messages WHERE session_id = $1", ("s1",)) # [{...}, {...}]
# Vector search (HNSW)
db.create_vector_store("emb", 3)
ids = db.insert_vectors("emb", [[1.0, 0.0, 0.0], [0.0, 1.0, 0.0]])
db.vector_search("emb", [1.0, 0.0, 0.0], k=1) # [(id, distance)]
API
| method | returns |
|---|---|
EmbeddedDatabase(path) / EmbeddedDatabase.in_memory() |
a handle |
query(sql, params=None) |
list[dict] |
execute(sql, params=None) |
affected row count (int) |
execute_many(sql, rows) |
total affected (int) |
vector_search(store, query, k) |
list[(id, distance)] |
create_vector_store(name, dimensions) / insert_vectors(store, vectors) |
— / list[id] |
flush() |
— |
params is a tuple/list binding positionally to $1..$n. The GIL is released
around every engine call, so multiple Python threads can query concurrently.
Build from source
pip install maturin
maturin develop -m bindings/python/Cargo.toml # editable install into the active venv
maturin build --release -m bindings/python/Cargo.toml # abi3 wheel in target/wheels/
Metadata
Release files for heliosdb-nano-embedded 4.14.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| heliosdb_nano_embedded-4.14.0-cp38-abi3-manylinux_2_28_x86_64.whl | CPython 3.8 | abi3 | Linux glibc 2.28+ x86-64 | Details for heliosdb_nano_embedded-4.14.0-cp38-abi3-manylinux_2_28_x86_64.whl |
Release files / heliosdb_nano_embedded-4.14.0-cp38-abi3-manylinux_2_28_x86_64.whl
| Download URL | heliosdb_nano_embedded-4.14.0-cp38-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 10.2 MB |
| Tags | CPython 3.8 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
182d91bf642f35f6cd1e05e4d5dbea50724d4b7656a25aee4867c7579cec6a47
|
|
BLAKE2b-256 checksum How to use checksums |
7658551399eac0d2dc38747fd806850f888a31c11f3829bde15f423d0fd8ec9d
|
| 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 Aug 21, 2026.
Transparency logSecurity for heliosdb-nano-embedded 4.14.0
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.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for heliosdb_nano_embedded-4.14.0-cp38-abi3-manylinux_2_28_x86_64.whl
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 Aug 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.