This release is a pre-release and may not be stable for production use.
Pyplines Python SDK
Python 3.14 typed Action handlers:
from pyplines.actions import Context, Inputs, Outputs
class EchoInputs(Inputs):
message: str
class EchoOutputs(Outputs):
message: str
def handler(inputs: EchoInputs, context: Context) -> EchoOutputs:
context.log("Started")
return EchoOutputs(message=inputs.message)
Declare handler = "my_action:handler" under [project.entry-points."pyplines.action"] in pyproject.toml. Use pyplines-action init, validate, test and push to build and publish the image with its captured schema. Actions execute synchronously; timeouts and container lifecycle belong to the runner.
Install pyplines[client] for from pyplines.client import Client. The operator CLI is a separate distribution, pyplines-cli.
Execution context and logs
Context exposes invocation_id, scratch_dir (temporary /tmp space), and log:
context.log("Action started")
context.log("Service restarted", level="info", service="payments", elapsed_ms=420)
context.log("Retrying connection", level="warning", attempt=2)
- Levels are
debug,info,warning, anderror; explicit logs default toinfo. - Custom JSON-compatible attributes are nested under
fields. Dictionary keys MUST be strings; numbers MUST be finite. Arbitrary Python objects are not serialized. - Messages MUST be at most 4,096 characters. Encoded fields MUST fit within 8 KiB;
the complete JSON record MUST fit within 16 KiB. Invalid or oversized calls raise
ValueErrorwithout discarding fields or consuming a sequence number. - Emission is serialized across threads. Each record is flushed immediately.
stream="stderr"is independent of severity. Captured stdout defaults toinfo; captured stderr defaults toerror. Large captured writes are split into records.- Logs MUST NOT contain secrets. No automatic secret redaction is provided. The runner withholds server log collection for sensitive executions; authors must still avoid writing secrets to container stdout/stderr.
- Logs retain sequence, UTC timestamp, stream, message, level, and optional fields.
The CLI renders concise lines;
--jsonpreserves the full records.
SDK base classes are Inputs and Outputs; singular imports are no longer supported.
Rebuild Action images after updating the SDK. Previously published images retain their
embedded SDK and can continue executing with their captured contracts.
1 maintainer
Metadata
1 maintainer
Release files for pyplines 2026.10.1rc11
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| pyplines-2026.10.1rc11.tar.gz | 10.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyplines-2026.10.1rc11-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 20.5 kB
Release files / pyplines-2026.10.1rc11.tar.gz
| Download URL | pyplines-2026.10.1rc11.tar.gz |
|---|---|
| Size | 10.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
583ebfc6a4ea41ece8484b178797bf0e363fe423dd5fa84ff14a857c04c0bb4f
|
|
BLAKE2b-256 checksum How to use checksums |
589d97aa9b4210dbfe9ee466c5a87d0727fcb8056be84e9a1b0a6fac233b48de
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 15, 2026.
Transparency logRelease files / pyplines-2026.10.1rc11-py3-none-any.whl
| Download URL | pyplines-2026.10.1rc11-py3-none-any.whl |
|---|---|
| Size | 9.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
71bf102896bd0302724c0934712e79d9efa9e99b5193f9a1752b6cce0d5f3ab4
|
|
BLAKE2b-256 checksum How to use checksums |
a7ffb8b544edd18a3410e39a204f694c8c992e04bd6f372c3398b303f2d4e2e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 15, 2026.
Transparency log
