toolchest
Toolchest is a collection of generally useful functions that can be reused in various settings.
Find the most recent documentation at https://toolchest.readthedocs.io.
Notes
This library only supports python 3. Some features may still work with python 2.7 but not all of the syntax and features may be compatible. Prettytable can be used, but is optional.
Installing
toolchest is available on PyPI; it can be installed by running::
pip install toolchest
Alternatively, one could also clone this repository and run::
pip install --editable .
Development
toolchest supports both standard python virtual environment setups and pipenv, which is integrated into our Makefile. To set up a pipenv-based development enironment, you can simply run::
make dev
This will install our dev environment for the package via pipenv. It is installed with --user, so it does not affect your site-packages. Pipenv creates a unique virtualenv for us, which you can activate via::
pipenv shell
See the pipenv documentation for more detail.
If you prefer to use pip directly in your venv, specify the following requirements files:
- requirements.txt
- test-requirements.txt
There is also a dist-requirements.txt, if you will be building the project for distribution.
Documentation
To build the documentation on your checkout, simply run::
make docs
Alternatively, to install via pip directly, include the following requirements files:
- requirements.txt
- docs-requirements.txt
Contributing
All new code should include tests that exercise the code and prove that it works, or fixes the bug you are trying to fix. Any Pull Request without tests will not be accepted. See CONTRIBUTING.rst for more details.
Building
If you wish to build a local package for testing at any time, you can simply run::
make dist
this will build a package with a .dev extension that you can install for testing and verification.
Acknowledgements
This code contains a derivative work of 'rpmvercmp' from RPM 4.14.1.
Metadata
Release files for toolchest 0.0.13
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 | |
|---|---|---|---|---|
| toolchest-0.0.13.tar.gz | 37.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| toolchest-0.0.13-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 66.7 kB
Release files / toolchest-0.0.13.tar.gz
| Download URL | toolchest-0.0.13.tar.gz |
|---|---|
| Size | 37.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
47767611a277ca1c0fd7ba66ba6859c608b48d8176489f85885768eb17892465
|
|
BLAKE2b-256 checksum How to use checksums |
dd6b015d9b247871b99cb99f47a3e73b1f2e94b9beb9f543867f009f50ca2e48
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.13
|
Release files / toolchest-0.0.13-py3-none-any.whl
| Download URL | toolchest-0.0.13-py3-none-any.whl |
|---|---|
| Size | 29.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f0fbdc5ccece0debc4a0342b6814167aa31af131d70d9e5770d6db437bd35900
|
|
BLAKE2b-256 checksum How to use checksums |
dc0086a1314cc4c609bfb436be504410abfb6752b1a821c30549885aea7a13bf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.9.13
|
Security for toolchest 0.0.13
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.