Pipelines may wish to use tee to cache intermediate steps as a failsafe in case of a downstream failure. This strategy is limited by the fact that the speed at which tee writes to disk is bottlenecked by the speed at which the downstream pipeline reads from its stdout. Therefore tee cannot finish writing to disk before its input has been completely output by the downstream pipeline. An option is to store all input from stdin in an in-memory buffer, but this can lead to out-of-memory failures. The steed command overcomes this limitation by writing to the on-disk file continuously, while simultaneously reading from it to obtain a size-limited buffer queue that is output to stdout. This allows steed to complete writing to disk before it has finished outputting to downstream commands, improving its utility as a cacheing mechanism.
1 maintainer
Metadata
1 maintainer
Release files for steed 0.2.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 | Provenance | Actions |
|---|---|---|---|---|
| steed-0.2.0.tar.gz | 2.4 kB | Without provenance | Details for steed-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| steed-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for steed-0.2.0-py3-none-any.whl |
Total release size: 5.4 kB
Release files / steed-0.2.0.tar.gz
| Download URL | steed-0.2.0.tar.gz |
|---|---|
| Size | 2.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4ffc8089812471d1d29366e1f38a8df1f82de21eb787e0a1af3597af8f600031
|
|
BLAKE2b-256 checksum How to use checksums |
bc0c6af8bbec7bad1ab178d71e016080a4533cba65e80286c2de2970defecba1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 colorama/0.4.4 importlib-metadata/7.0.1 keyring/24.3.0 pkginfo/1.9.6 readme-renderer/34.0 requests-toolbelt/1.0.0 requests/2.31.0 rfc3986/1.5.0 tqdm/4.66.1 urllib3/1.26.5 CPython/3.10.12
|
Release files / steed-0.2.0-py3-none-any.whl
| Download URL | steed-0.2.0-py3-none-any.whl |
|---|---|
| Size | 3.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8b4bd3c11bb71cb03b8f5e0d45c83b71a0d414e09a019b450ef1070a6e6115ef
|
|
BLAKE2b-256 checksum How to use checksums |
49780c36cce66f06568439f452411ee7f12a1d61effa8064b5eb7d9f5921f643
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.8.0 colorama/0.4.4 importlib-metadata/7.0.1 keyring/24.3.0 pkginfo/1.9.6 readme-renderer/34.0 requests-toolbelt/1.0.0 requests/2.31.0 rfc3986/1.5.0 tqdm/4.66.1 urllib3/1.26.5 CPython/3.10.12
|
Security for steed 0.2.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.
