About
Elastic Pipes defines a simple composition system in Python. The components, named pipes, are executed in sequence and a state is passed through from one to the next.
It looks like how UNIX pipes allow composing independent tools on the command line; indeed you can invoke Elastic Pipes in such way. Differently from UNIX pipes though, each component adds new content to the state which is otherwise passed down in the sequence as-is.
2 maintainers
Release files for elastic-pipes 0.7.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| elastic_pipes-0.7.0.tar.gz | 23.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| elastic_pipes-0.7.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 49.8 kB
Release files / elastic_pipes-0.7.0.tar.gz
| Download URL | elastic_pipes-0.7.0.tar.gz |
|---|---|
| Size | 23.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ade12325e94b761a9bfec22a676ea4a652537c78b5ea9486d85513f58086bbd
|
|
BLAKE2b-256 checksum How to use checksums |
5a765522303093e70162f2d40684f8f20cb00d827c572d49dba556de19a5067d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 1, 2025.
Transparency logRelease files / elastic_pipes-0.7.0-py3-none-any.whl
| Download URL | elastic_pipes-0.7.0-py3-none-any.whl |
|---|---|
| Size | 26.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b539e04581afcfa6476f39d889ad69b6bee2d074e331e3086090dbfb953cefa3
|
|
BLAKE2b-256 checksum How to use checksums |
f023a1b02c435411aa6d233fb4a34362a9d6ed865daff06ccb4bb78aa74fab1f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 1, 2025.
Transparency log
