dirigent-client
The dirigent API contract: typed wire schemas and an async Python client.
from datetime import timedelta
from dirigent_client import Dirigent
async with Dirigent(url="https://dirigent.example.org", token=token) as dg:
plan = await dg.pipelines.apply("pipelines/daily-climate-load.yaml", dry_run=True)
run = await dg.pipelines.run("daily-climate-load", params={"day": "2026-08-29"})
final = await dg.runs.wait(run.run_id, timeout=timedelta(hours=2))
async for entry in dg.runs.follow_logs(run.run_id):
print(entry.message)
The package holds the pydantic schemas for every request and response the REST API speaks,
and dirigent-server imports them, so the client and the server can never disagree about a
shape. It depends on dirigent-common, httpx2, pydantic, and pyyaml, and on nothing else in the
workspace.
docs/python.md has the worked examples, and examples/python/ has six runnable scripts.
1 maintainer
Metadata
1 maintainer
Release files for dirigent-client 0.26.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 | Provenance | Actions |
|---|---|---|---|---|
| dirigent_client-0.26.0.tar.gz | 43.0 kB | With provenance | Details for dirigent_client-0.26.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dirigent_client-0.26.0-py3-none-any.whl | Python 3 | none | any | Details for dirigent_client-0.26.0-py3-none-any.whl |
Total release size: 102.5 kB
Release files / dirigent_client-0.26.0.tar.gz
| Download URL | dirigent_client-0.26.0.tar.gz |
|---|---|
| Size | 43.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
203499eb52144746368c635926f7deab37068da8e8b9df13126e5abfe3be11c0
|
|
BLAKE2b-256 checksum How to use checksums |
f3577942e182eb723b4480799852358f7b6bd57051c43a1ae690b4aeb7bfef02
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 29, 2026.
Transparency logRelease files / dirigent_client-0.26.0-py3-none-any.whl
| Download URL | dirigent_client-0.26.0-py3-none-any.whl |
|---|---|
| Size | 59.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f4bf2876fc3ccc66a85a588bf7d8905853539b6cb10de55de47bb9ef3292614e
|
|
BLAKE2b-256 checksum How to use checksums |
efa984b139c1b61d35980eb045f5ef50caca276d7e08b52c30daa304be15d5b5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 29, 2026.
Transparency logSecurity for dirigent-client 0.26.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
Both files in this release have been uploaded with provenance metadata.
Attestation for dirigent_client-0.26.0.tar.gz
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 Oct 29, 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.
