Classes and methods for integrating code inside a docker image into a processing pipeline, using redis for exchanging data.
Changelog
0.0.4 (2023-07-25)
added the redis_timeout parameter to the argparse options to make the pubsub thread sleep_time parameter configurable from the command-line (the default is now 0.01 instead of 0.001 to avoid high CPU load)
the create_parser method can now specify the default values for: host, port, db, channel_in, channel_out, sleep_time
0.0.3 (2023-07-10)
fixed password support when accessing environment variable
0.0.2 (2023-07-07)
added support for supplying a password to use for the Redis connection (–password/–password_env)
0.0.1 (2021-09-22)
initial release
Metadata
Release files for redis-docker-harness 0.0.4
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 | |
|---|---|---|---|---|
| redis-docker-harness-0.0.4.tar.gz | 4.3 kB | Without provenance | Details |
Release files / redis-docker-harness-0.0.4.tar.gz
| Download URL | redis-docker-harness-0.0.4.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
592bf2f4e173f51c19a2c733ce169836ad54208319bed43440a7e9fc5f31eed8
|
|
BLAKE2b-256 checksum How to use checksums |
43556bb5c10a8a1803a0ac06925f231ba02f5344ac645b97420ea578f3cbddef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.2 importlib_metadata/4.8.1 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Security for redis-docker-harness 0.0.4
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.