Skip to main content

pyronites

Official Python client for the Pyronites backend.

Supabase-style API, zero mandatory paid services — point it at your own backend URL + API key.

Install

# Development (from this repo)
pip install -e ./pyronites

# From PyPI (after publish)
pip install pyronites

Requires Python 3.10+.

5-minute setup

export PYRONITES_URL="https://your-backend.example.com"
export PYRONITES_KEY="pyro_live_..."
from pyronites import create_client

client = create_client()

# Auth (optional)
client.auth.sign_in("user@example.com", "password")
print(client.auth.user())

# Tables
note = client.table("notes").insert({"title": "Hello", "body": "World"})
for row in client.table("notes").select().limit(10):
    print(row)
client.table("notes").update({"title": "Updated"}).eq("id", note["id"])
client.table("notes").delete().eq("id", note["id"])

# Storage
meta = client.storage.upload("photo.jpg")
data = client.storage.download(meta["id"])
client.storage.remove(meta["id"])

# Local-only / cache tables (optional)
client = create_client(
    local_tables=["settings"],
    cache_tables=["catalog"],
    local_db_path="./.pyronites_local.db",
)
client.table("settings").insert({"theme": "dark"})
client.pull("catalog")

Config

Source Variables / args
Env PYRONITES_URL, PYRONITES_KEY, optional PYRONITES_LOCAL_DB
Constructor create_client(url=..., key=..., timeout=30, local_tables=..., cache_tables=..., remote_tables=..., local_db_path=...)

Args override env. Missing URL raises a clear error at create time.

Security: never put a powerful service key in a public frontend.

Public API

See docs/syntax.md.

Development

cd pyronites
pip install -e ".[dev]"
pytest

License

MIT

Metadata

Release files for pyronites 1.3.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pyronites 1.3.0
File Size Uploaded Provenance
pyronites-1.3.0.tar.gz 20.4 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for pyronites 1.3.0
File Interpreter ABI Platform
pyronites-1.3.0-py3-none-any.whl Python 3 none any Details

Total release size: 34.2 kB

Release files / pyronites-1.3.0.tar.gz

Download URL pyronites-1.3.0.tar.gz
Size 20.4 kB
Tags Source
SHA-256 checksum
How to use checksums
1a0e7e85ef6ed62afd7e26210365704255e278b159f0c260eeb7e3d4f4f49005
BLAKE2b-256 checksum
How to use checksums
f7dddf9656a02700a334ef6cefdd64314315244f15b333b3f85192385db1dd69
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Release files / pyronites-1.3.0-py3-none-any.whl

Download URL pyronites-1.3.0-py3-none-any.whl
Size 13.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ffad0afcbc006645928a77ecde0c3c5cbe9be53242dca9c2372cc4c1707118c5
BLAKE2b-256 checksum
How to use checksums
231e96685e9acb3fa10f2e78ea7e4450444e09cd9788eb1e06ed774ad1695821
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Security for pyronites 1.3.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page