adag
Another DAG: a cached, content-addressed DAG engine for Python data pipelines.
Install
pip install adag
Requires Python 3.13+.
Quickstart
Each step is a frozen dataclass. Call a step to wire it into the graph, then run the
graph with a Pipeline.
from dataclasses import dataclass
from pathlib import Path
from pydantic import BaseModel
from adag import InputParam, Pipeline, Step
class Number(BaseModel):
value: int
@dataclass(frozen=True)
class Square(Step[Number]):
def run(self, x: int) -> Number:
print("computing square")
return Number(value=x * x)
@dataclass(frozen=True)
class AddOne(Step[Number]):
def run(self, n: Number) -> Number:
return Number(value=n.value + 1)
x = InputParam[int]("x")
total = AddOne()(n=Square()(x=x))
pipeline = Pipeline(total, cache_dir=Path("cache"))
print(pipeline.execute(x=4)) # computes both steps
print(pipeline.execute(x=4)) # served from the cache
The second run reads both results from cache/ and does not call Square.run again:
computing square
value=17
value=17
(output trimmed: structlog lines removed)
Why adag
A step's cache key is a hash of its fields, its inputs, and its source code. Change any of them and that step and everything downstream recompute; nothing else does. Use it for data and ML pipelines where steps are slow and you rerun the graph often.
Key features
- Content-addressed cache: a code edit invalidates only the steps it touches.
- Sync and async steps (
Step,AsyncStep), with a parallel executor. FanOutStepruns a sub-graph per key;BatchStepcaches each item on its own.- Cache backends: filesystem, memory, SQLite, SQLAlchemy (
adag[sql]), Redis (adag[redis]). - Save a pipeline to disk and load it back with identical hashes.
- SVG rendering of the graph, and an
adag run pipeline.pyCLI. - Run fan-out branches in subprocesses or AWS Batch jobs, joined through the cache.
Links
- Documentation: https://cardona-oss.gitlab.io/adag/
- Source: https://gitlab.com/cardona-oss/adag
- Issues: https://gitlab.com/cardona-oss/adag/-/issues
- PyPI: https://pypi.org/project/adag/
- Changelog: CHANGELOG.md
Contributing
Developer setup, the dev loop, and the release process live in
CONTRIBUTING.md. In short: uv sync && make install-hooks, then
make check runs the same gate CI runs.
License
MIT © 2026 Jorge Cardona (see LICENSE).
Metadata
Release files for adag 0.2.4
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 | Actions |
|---|---|---|---|---|
| adag-0.2.4.tar.gz | 110.3 kB | Without provenance | Details for adag-0.2.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| adag-0.2.4-py3-none-any.whl | Python 3 | none | any | Details for adag-0.2.4-py3-none-any.whl |
Total release size: 195.4 kB
Release files / adag-0.2.4.tar.gz
| Download URL | adag-0.2.4.tar.gz |
|---|---|
| Size | 110.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2968621fe345719c36b67ac3e13cf2caebca7f5abf87e53a726a52bae3c102c
|
|
BLAKE2b-256 checksum How to use checksums |
4d2cfc6f7a356442e1527758487f5323754bc471eaf2bc880df6a9cd8add2607
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.19 {"installer":{"name":"uv","version":"0.11.19","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / adag-0.2.4-py3-none-any.whl
| Download URL | adag-0.2.4-py3-none-any.whl |
|---|---|
| Size | 85.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d4a8792208d7bdb86327e4691de4564b690c0dd95f97203aad20191b50fdc1dc
|
|
BLAKE2b-256 checksum How to use checksums |
d97a0ae4feba4a28e9f3ba7f924fa33bbc30c56b6d0cd0c16e9d97ea4e5706d5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.11.19 {"installer":{"name":"uv","version":"0.11.19","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for adag 0.2.4
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.