sahou (Python runtime)
Typed communication over real Zenoh, using just a contract (descriptor.json) plus a node name. The
boundary semantics are delegated to the Rust core (sahou-core / sahou._core); this glue layer only
handles the transport (zenoh-python) and threading.
Usage
import sahou
node = sahou.connect("descriptor.json", node="sensor") # default = automatic discovery on the same LAN
# (the path is up to you. When using the output of `sahou gen --out-dir gen`, use "gen/descriptor.json")
node.publish("touch", {"x": 0.5, "phase": "move"}) # a NO is SahouRejected (nothing is put)
@node.subscribe("cue")
def on_cue(payload): ... # a NO never reaches the handler (goes to on_reject)
res = node.query_confirmed("get_state", {"sel": "levels"}) # 200/400/500 equivalent + smart retry
node.answer("get_state", lambda req: {"level": 3})
Development
uv venv && uv pip install maturin pytest "eclipse-zenoh>=1.9,<2"
.venv/Scripts/maturin develop # build the core with feature "python"
.venv/Scripts/python -m pytest tests/
- Contract version differences are decided by a handshake (contract queryable + verdict cache): additive = pass through / breaking = NO / unfetchable = conservative NO. There is no path that silently passes or drops.
- Not yet implemented (planned follow-ups): auto-launch of sahou link (for Node/browser, ②b) / tap, doctor, type stubs (②c).
1 maintainer
Metadata
1 maintainer
Release files for sahou 0.0.2
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 |
|---|---|---|---|---|
| sahou-0.0.2.tar.gz | 95.4 kB | With provenance | Details for sahou-0.0.2.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| sahou-0.0.2-cp310-abi3-win_amd64.whl | CPython 3.10 | abi3 | Windows x86-64 | Details for sahou-0.0.2-cp310-abi3-win_amd64.whl |
| sahou-0.0.2-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ x86-64 | Details for sahou-0.0.2-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
| sahou-0.0.2-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.10 | abi3 | Linux glibc 2.17+ ARM64 | Details for sahou-0.0.2-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
| sahou-0.0.2-cp310-abi3-macosx_11_0_arm64.whl | CPython 3.10 | abi3 | macOS 11.0+ ARM64 | Details for sahou-0.0.2-cp310-abi3-macosx_11_0_arm64.whl |
Total release size: 1.9 MB
Release files / sahou-0.0.2.tar.gz
| Download URL | sahou-0.0.2.tar.gz |
|---|---|
| Size | 95.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cbfb85dfdc1caf3649d520a681f748b48e37e447104e07375129dbbf177b075a
|
|
BLAKE2b-256 checksum How to use checksums |
dad1b9239f307fd5736781dd1115941152e0745cdf042ec6f9d2e99d3e71e844
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.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.
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 Jul 15, 2026.
Transparency logRelease files / sahou-0.0.2-cp310-abi3-win_amd64.whl
| Download URL | sahou-0.0.2-cp310-abi3-win_amd64.whl |
|---|---|
| Size | 354.4 kB |
| Tags | CPython 3.10 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
b120193c89b5c1618694f3f853fe4ceab3ed3134628b682123b407de938b3936
|
|
BLAKE2b-256 checksum How to use checksums |
5e485daed2a079eeab912384477f65a6882ee10038589667302c70e1560aa065
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.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.
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 Jul 15, 2026.
Transparency logRelease files / sahou-0.0.2-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | sahou-0.0.2-cp310-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 516.9 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
ee66c0e00e903bd0905b8308b6aaef4b4bf53ed40ded8ddac02554df2ab0c8df
|
|
BLAKE2b-256 checksum How to use checksums |
10bf96d84763f2e112a76047f776e2a24d2ac40694c249b3d190582d3a863804
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.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.
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 Jul 15, 2026.
Transparency logRelease files / sahou-0.0.2-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | sahou-0.0.2-cp310-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 507.7 kB |
| Tags | CPython 3.10 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
82861783eaa84148bb4f5b548702081f8d770a9c9081834e01bda771c7ac57aa
|
|
BLAKE2b-256 checksum How to use checksums |
cd8b03d51e90b2ce20829989571f79134aa070c0d1e339911082ac76cf5e0a6f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.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.
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 Jul 15, 2026.
Transparency logRelease files / sahou-0.0.2-cp310-abi3-macosx_11_0_arm64.whl
| Download URL | sahou-0.0.2-cp310-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 465.9 kB |
| Tags | CPython 3.10 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
38c61a5f66d917462ff50f3e5195107fdcf70b20455072d13d0c9d17aad37f56
|
|
BLAKE2b-256 checksum How to use checksums |
77d2268266bc18dcb417a9b3710a54d2fbaebc1f1f2d8cbba09d56bd47839477
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.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.
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 Jul 15, 2026.
Transparency logSecurity for sahou 0.0.2
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 5 files in this release have been uploaded with provenance metadata.
Attestation for sahou-0.0.2.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 Jul 15, 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.
