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, run 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.
Compatibility and local diagnostics
Stable authoring APIs are Inputs, Outputs, Context, and ActionError.
Stable releases within a calendar year retain backwards-compatible authoring APIs;
prereleases do not carry that guarantee. CalVer tags identify releases, while the
execution contract pyplines.action.v1 determines platform interoperability.
Actions carry their SDK/runtime and do not need to match the server release.
Declare a supported dependency requirement (exact pins are valid), commit uv.lock,
and upgrade deliberately with uv. Local tooling resolves the lock, not its own
release version, to choose Action bases.
pyplines-action run requests detailed local diagnostics through the supported
python -m pyplines.actions.development entry point. --source PATH uses source
without installing the Action; omitting it executes the installed Action.
--build PATH discovers the installed Action interface. --diagnostics accepts
detailed or concise; --capabilities reports versioned interface support.
Production entry points retain concise errors by default. Detailed diagnostics
never capture locals; exception messages and source lines are not automatically
redacted. Rebuild images with this SDK to obtain the new capabilities.
Output serialization
Output instances are revalidated before serialization, including constructed or mutated nested models. Field aliases and computed fields are supported. The wire output uses serialization aliases, and the captured output schema uses Pydantic's serialization mode, so computed fields and declared serializer return types match what consumers receive. Serializers run after validation, not as a way to repair invalid field values.
Rebuild matching SDK base images and Action images to adopt these changes; previously published images retain their embedded SDK.
1 maintainer
Metadata
1 maintainer
Release files for pyplines 2026.10.3rc1
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.3rc1.tar.gz | 20.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pyplines-2026.10.3rc1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.2 kB
Release files / pyplines-2026.10.3rc1.tar.gz
| Download URL | pyplines-2026.10.3rc1.tar.gz |
|---|---|
| Size | 20.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
19b7400057fd0c0b3399c08bd415949ef8cb771bd8b6f014eabf857460c9fb3b
|
|
BLAKE2b-256 checksum How to use checksums |
5079263f555733f0ed46ca3be4c3d05e3b698246527576d3031c4d3c088ae829
|
| 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 16, 2026.
Transparency logRelease files / pyplines-2026.10.3rc1-py3-none-any.whl
| Download URL | pyplines-2026.10.3rc1-py3-none-any.whl |
|---|---|
| Size | 15.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09e2820ed0543444edd994104fba1e3456698afb5177dfe7fe884efac12ea387
|
|
BLAKE2b-256 checksum How to use checksums |
79b77f19530127ae63bee2cfc5c5f5e1a79b9485f434ac0d3108f7e87b5a6965
|
| 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 16, 2026.
Transparency log
