ttr-plan-proto (Python)
Pre-generated Python message classes for the TTR-P plan pipeline wire formats:
plan.v1, transdsl.v1, dfdsl.v1. Importable at their canonical module paths,
e.g. from org.tatrman.plan.v1 import plan_pb2.
Canonical source of truth: the .proto files in the sibling Kotlin module
../../kotlin/ttr-plan-proto/src/main/proto/. tatrman owns the wire format once
(decision TR-3); this wheel and the org.tatrman:ttr-plan-proto Maven jar are the
per-language published artifacts. Formerly generated inside kantheon shared/proto;
transferred at f2e2efb (2026-07-06). See docs/ttr-translator/.
Build
Pure-Python wheel (py3-none-any). The build hook (hatch_build.py) runs
grpcio-tools' bundled protoc over the sibling .proto files — no JVM needed.
The generated src/org/** tree is gitignored and regenerated on every build.
uv build --wheel # or: pipx run build --wheel
uv run --with protobuf --with pytest pytest tests/
Released to PyPI via python-plan/v<x.y.z> (trusted publishing); versioned in
lockstep with the Maven kotlin-translator/v* pair by convention.
Governance
Proto changes are driven by kantheon runtime needs (typically PipelineContext);
they arrive as PRs to this repo, which cuts a prompt lockstep release. Field
numbers/types are append-only within v1 (see docs/ttr-translator/architecture/contracts.md §2).
Metadata
Release files for ttr-plan-proto 0.12.11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ttr_plan_proto-0.12.11-py3-none-any.whl | Python 3 | none | any | Details for ttr_plan_proto-0.12.11-py3-none-any.whl |
Release files / ttr_plan_proto-0.12.11-py3-none-any.whl
| Download URL | ttr_plan_proto-0.12.11-py3-none-any.whl |
|---|---|
| Size | 17.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
568fbde9b16a9d258dbcbdee3d11ec479ea13ed7bfea90d95fcba2c47bf1ada6
|
|
BLAKE2b-256 checksum How to use checksums |
2a9e2d1d1848169d4eeab8d01752241bc8999928905b07680221205ddd127812
|
| 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 24, 2026.
Transparency logSecurity for ttr-plan-proto 0.12.11
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 1 file in this release has been uploaded with provenance metadata.
Attestation for ttr_plan_proto-0.12.11-py3-none-any.whl
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 24, 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.