This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Consider using release 2.1.1 instead.
Reason given by maintainers: Deprecated
General purpose bash and python library for zeroincombenze(R) tools
Features:
xuname: unix/linux platform recognizer (tested on various environments)
parseoptargs: line command parser; expands python argparse and adds same functionalities to bash scripts
tracelog: manage tracelog (only bash)
findpkg: find package in file system (only bash)
run_traced: execute (or dry_run) shell command (only bash)
CFG: local dictionary values from config file like python ConfigParser (only bash)
1 maintainer
Metadata
1 maintainer
Release files for z0lib 1.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 | Actions |
|---|---|---|---|---|
| z0lib-1.0.4.tar.gz | 22.1 kB | Without provenance | Details for z0lib-1.0.4.tar.gz |
Release files / z0lib-1.0.4.tar.gz
| Download URL | z0lib-1.0.4.tar.gz |
|---|---|
| Size | 22.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ea5ef10d4df3a2adaf42f6de5cdedcc9dc7cc527501b1111abbf04c9fecbb01
|
|
BLAKE2b-256 checksum How to use checksums |
45632b6f4a2dec80962adcc5a3ded54f0570732223a3272f2ab21cff2e9183ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.4.2 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.8.0 tqdm/4.30.0 CPython/3.8.10
|
Security for z0lib 1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
