agni (Python client)
A typed Python client for agni. It calls the agni CLI or a running agni serve and returns the
wire contract's own message classes, generated from protos/agni/v1.
pip install 'agni-eda[xlsx]' # a release, from PyPI
pip install -e 'clients/python[xlsx]' # a checkout
The distribution is agni-eda because PyPI's agni is an unrelated project, and the import is
agni. Match its version to the agni binary or server it talks to.
from agni import Client, CliTransport, ConnectTransport
c = Client(CliTransport("agni", mounts={"tut": "examples/tutorial-project"}))
# or: c = Client(ConnectTransport("http://127.0.0.1:8080"))
snap = c.ingest("mount://tut/designs/gateway")
resp = c.run_query(snapshot=snap, query='component.class(?c, "resistor") => ?c')
c.delete_snapshot(snap)
Every question names a snapshot, a design loaded once under one config (agni issue 1061). ingest
returns its name, and takes the board_uri, as_named and overlay a request used to carry, and
flatten_hierarchy, which reads a hierarchical EDIF netlist whole as --flatten-hierarchy does.
A server holds a snapshot until it is deleted or evicted, and refuses one whose files changed. The
client keeps the definition of each snapshot it ingested, so a question naming one the server lost is
asked again after ingesting it under the same name, and one whose files changed after updating it, as
the viewer does (agni issue 1067). A snapshot this client did not ingest, or deleted, still raises
AgniError with code not_found, and AgniError.snapshot_unavailable says which. The CLI transport has
no server, so it keeps each definition itself under a name it mints (snapshots/cli-1) and turns it
back into flags for every command it runs.
The guide, docsite/content/build/other-languages.md, covers choosing a transport, which rpcs the
CLI covers, where the two differ today, and writing tables to xlsx.
examples/audit_workbook.pywrites a five-sheet audit workbook of the tutorial board, asking its four tables as one query set (run_queries) so the design is read once.examples/revision_audit.pycompares two revisions of the gateway and audits the newer one, writing a workbook and a markdown summary that lists each tab still to be built.make exercise-revision-auditruns it with the checkout's binary (agni issue 843).make proto-pyregeneratessrc/agni/v1. Never edit it by hand;make proto-checkfails on drift.make python-testruns the suite against a built binary and a real server.make python-dist V=vX.Y.Zbuilds the sdist and wheel a release publishes intodist/pythonand installs the wheel into a fresh venv to check it. The release workflow runs it, and the gate runspython-dist-check.
Metadata
Release files for agni-eda 0.3.13
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 |
|---|---|---|---|---|
| agni_eda-0.3.13.tar.gz | 107.9 kB | With provenance | Details for agni_eda-0.3.13.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agni_eda-0.3.13-py3-none-any.whl | Python 3 | none | any | Details for agni_eda-0.3.13-py3-none-any.whl |
Total release size: 233.8 kB
Release files / agni_eda-0.3.13.tar.gz
| Download URL | agni_eda-0.3.13.tar.gz |
|---|---|
| Size | 107.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
874e1aa92a037946040eccb2e724954e1a4d6deaaada2096c4b2bd21b81911e6
|
|
BLAKE2b-256 checksum How to use checksums |
98623b1174b61b98810f734fb51c7c2cf273e092093b6a3eb407bf2008793869
|
| 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 30, 2026.
Transparency logRelease files / agni_eda-0.3.13-py3-none-any.whl
| Download URL | agni_eda-0.3.13-py3-none-any.whl |
|---|---|
| Size | 125.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7c7930018a2a2667195829484bdc6a348546467d1dab0ceba46ea25afebf0ce2
|
|
BLAKE2b-256 checksum How to use checksums |
4ec47f97ae296beaf582ff7fb3b0b0803178a6423849905a80a43b80986a46f5
|
| 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 30, 2026.
Transparency logSecurity for agni-eda 0.3.13
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 2 files in this release have been uploaded with provenance metadata.
Attestation for agni_eda-0.3.13.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 30, 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.