Zambeze
Documentation for Zambeze can be found on ReadTheDocs.
Get in Touch
The main channel to reach the Zambeze team is via the support email: support@zambeze.org.
Bug Report / Feature Request: our preferred channel to report a bug or request a feature is via
Zambeze's Github Issues Track.
Installation
Dependency installation should proceed similar to any python package.
pip install -r requirements.txt .
Zambeze CLI
zambeze --help
Development Environment
Code Formatting
Zambeze's code uses Black, a PEP 8 compliant code formatter, and Flake8, a code style guide enforcement tool. To install the these tools you simply need to run the following:
pip install flake8 black
Before every commit, you should run the following:
black .
flake8 .
If errors are reported by flake8, please fix them before commiting the code.
Running Tests
There are a few dependencies that need to be installed to run the pytest, if you installed the requirements.txt file then this should be covered as well.
pip install pytest
From the root directory using pytest we can run:
python3 -m pytest -m unit -sv
Some tests should only be run from the context of the GitLab runner these can be run with:
python3 -m pytest -m gitlab_runner -sv
Metadata
Release files for zambeze 0.1
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 |
|---|---|---|---|---|
| zambeze-0.1.tar.gz | 67.5 kB | Without provenance | Details for zambeze-0.1.tar.gz |
Release files / zambeze-0.1.tar.gz
| Download URL | zambeze-0.1.tar.gz |
|---|---|
| Size | 67.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
936ee3c6ca4269796998d7a134091cade91a12478ccc5d5be349be00b48974c9
|
|
BLAKE2b-256 checksum How to use checksums |
8e49e6cf80231d66e59f528677633ab73c4a836ad1d8db19fea23f350ac326d7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.9.12
|
Security for zambeze 0.1
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.