pyrosome
Versioned, append-only storage for polars data frames.
pyrosome stores data frames on disk as parquet (or CSV) files, keeps every version you write, and reads them back as lazy frames. Several processes can read, write and append to the same data at once without overwriting each other or seeing half-written data.
Purpose
Saving data frames to files is easy. Keeping those files trustworthy is harder:
- overwriting a file loses the previous data, and a crash halfway through can leave it corrupt;
- two processes writing at once can clobber each other;
- a reader can pick up a file that is still being written.
pyrosome handles this with a small, predictable layout on the filesystem. There is no database or server to run.
Project summary
- Versioned: every
writecreates a new version (v0,v1, …). Older versions stay on disk until you remove them, so rollbacks and audits are simple. - Append-only:
appendadds a new file to the latest version and never rewrites existing files. Columns are reordered and cast to match the stored data. - Safe with several processes: versions are claimed with an atomic
mkdir, appends claim their index by exclusively creating a marker file so they never overwrite each other, and the manifest naming the latest version is replaced in one step. - Lazy:
readreturns apolars.LazyFrame, so filters and column selections are pushed down into the file scan. - Parquet or CSV:
ParquetDalstores parquet;CsvDalhas the same API and stores CSV for people and tools that need to open the files directly.
Data is organised into profiles, named by one or more keys:
data/
└── sales/
└── orders/ # profile for keys ("sales", "orders")
├── manifest.json # {"latest_data_dir": "v1"}
├── v0/
│ ├── 0.parquet # written by write()
│ └── 1.parquet # added by append()
└── v1/
└── 0.parquet
Platform support
pyrosome supports Windows, Linux and macOS, with the data directory on a local disk or an NFS share (NFSv3 or later).
SMB shares are supported as a lower priority. pyrosome aims to work on them, but they get less attention and testing, and some SMB setups have limitations. For example, they may ignore the read-only permission pyrosome sets on finished data files.
Install
pyrosome requires Python 3.14 or newer.
Add it to a uv project:
uv add pyrosome
Or install it into the current environment with pip:
pip install pyrosome
Development setup
uv sync --all-groups
This installs the development tools (pytest, ruff, ty, mypy, pylint) and the documentation tools (Sphinx, furo).
| Task | Command |
|---|---|
| Run tests, including every example in the docs and this README | uv run pytest |
| Lint and format | uv run ruff check and uv run ruff format |
| Type check | uv run ty check and uv run mypy src |
| Pylint | uv run pylint src |
| Build docs | uv run sphinx-build -W -b html docs docs/_build/html |
Quickstart
write creates a new version and returns its directory:
>>> from pathlib import Path
>>> import polars as pl
>>> from pyrosome import ParquetDal
>>> dal = ParquetDal(Path("data"))
>>> orders = pl.DataFrame(
... {"order_id": [1, 2, 3], "region": ["eu", "eu", "us"], "total": [9.5, 20.0, 7.25]}
... )
>>> dal.write(orders, "sales", "orders").as_posix()
'data/sales/orders/v0'
append adds a file to the latest version. Column order doesn't matter:
>>> more = pl.DataFrame({"total": [12.0], "order_id": [4], "region": ["us"]})
>>> dal.append(more, "sales", "orders").as_posix()
'data/sales/orders/v0/1.parquet'
read returns a LazyFrame over the latest version:
>>> (
... dal.read("sales", "orders")
... .filter(pl.col("region") == "eu")
... .select(pl.col("total").sum())
... .collect()
... .item()
... )
29.5
Writing again creates v1, and read now returns only the new data. The earlier version stays on disk:
>>> _ = dal.write(pl.DataFrame({"order_id": [10], "status": ["open"]}), "sales", "orders")
>>> dal.read("sales", "orders").collect().columns
['order_id', 'status']
>>> sorted(path.as_posix() for path in Path("data").rglob("[!.]*.*"))
['data/sales/orders/manifest.json', 'data/sales/orders/v0/0.parquet', 'data/sales/orders/v0/1.parquet', 'data/sales/orders/v1/0.parquet']
To store CSV instead, use CsvDal with the same methods. Keep each format in its own data directory, because a CSV write to a parquet profile hides the parquet data from ParquetDal:
>>> from pyrosome import CsvDal
>>> CsvDal(Path("exports")).write(orders, "sales", "orders").as_posix()
'exports/sales/orders/v0'
read raises FileNotFoundError for a profile with no data, and append raises ValueError if the columns don't match the stored data:
>>> dal.read("sales", "returns")
Traceback (most recent call last):
...
FileNotFoundError: Cannot find files for ('sales', 'returns')
Documentation
The full documentation is in docs/ and covers concepts, 14 recipes (compaction, rollbacks, pruning old versions, multi-process ingest and more), and the API reference. Build it with:
uv run sphinx-build -W -b html docs docs/_build/html
Then open docs/_build/html/index.html.
License
MIT. See LICENSE.
Metadata
Release files for pyrosome 0.1.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pyrosome-0.1.12.tar.gz | 16.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyrosome-0.1.12-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 35.4 kB
Release files / pyrosome-0.1.12.tar.gz
| Download URL | pyrosome-0.1.12.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
242fa49e6c7c6cd25df4ce8746b1c630b64029080be1f2d9e35005ceb07789e5
|
|
BLAKE2b-256 checksum How to use checksums |
15f375df614a1d98b572e18531ccade4649251a9e0bac3cec9d634035af89b21
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / pyrosome-0.1.12-py3-none-any.whl
| Download URL | pyrosome-0.1.12-py3-none-any.whl |
|---|---|
| Size | 18.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9427a2e2cc65467f2ff32f989d4204cf6498da7a1a53d9659df254394eb928a5
|
|
BLAKE2b-256 checksum How to use checksums |
deae9f181f08d6a72af65c0018e38b90708fb0fb59e3b539483d7557fb59b926
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.5 {"installer":{"name":"uv","version":"0.13.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for pyrosome 0.1.12
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.