Legion Utils
Utilities for Legion Reporters and Monitors
Usage
TODO
Installation & Setup
To install legion-utils with pip execute the following:
pip install /path/to/repo/legion-utils
If you don't want to re-install every time there is an update, and prefer to just pull from the git repository, then use the -e flag.
Development
Standards
- Be excellent to each other
- Code coverage must be at 100% for all new code, or a good reason must be provided for why a given bit of code is not covered.
- Example of an acceptable reason: "There is a bug in the code coverage tool and it says its missing this, but it's not".
- Example of unacceptable reason: "This is just exception handling, its too annoying to cover it".
- The code must pass the following analytics tools. Similar exceptions are allowable as in rule 2.
pylint --disable=C0111,W1203,R0903 --max-line-length=100 ...flake8 --max-line-length=100 ...mypy --ignore-missing-imports --follow-imports=skip --strict-optional ...
- All incoming information from users, clients, and configurations should be validated.
- All internal arguments passing should be typechecked whenever possible with
typeguard.typechecked
Development Setup
Using PDM install from inside the repo directory:
pdm install
IDE Setup
PyCharm
You're going to want to install the Pydantic PyCharm Plugin for proper type-safety warnings and stuff.
Testing
All testing should be done with pytest which is installed with the dev requirements.
To run all the unit tests, execute the following from the repo directory:
pdm run pytest
This should produce a coverage report in htmlcov/
While developing, you can use watchexec to monitor the file system for changes and re-run the tests:
watchexec -r -e py,yaml pdm run pytest
To run a specific test file:
pdm run pytest tests/unit/test_core.py
To run a specific test:
pdm run pytest tests/unit/test_core.py::test_hello
For more information on testing, see the pytest.ini file as well as the documentation.
Building & Publishing to PyPi
You can use Twine to publish this code to PyPi assuming you have an account and the relevant project permissions. This can be configured using a ~/.pypirc file like so:
[distutils]
index-servers =
pypi
testpypi
[testpypi]
username = __token__
password = <PYPI TOKEN>
[pypi]
username = __token__
password = <PYPI TOKEN>
You can get the PyPi Tokens here: https://pypi.org/help/#apitoken
Once you have that set up, you can build, publish to the test server, and then the prod server with the following commands:
pdm build;
pdm publish-test; # test
pdm publish-prod; # prod
Metadata
Release files for legion-utils 0.6.5
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 |
|---|---|---|---|---|
| legion-utils-0.6.5.tar.gz | 105.2 kB | Without provenance | Details for legion-utils-0.6.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| legion_utils-0.6.5-py3-none-any.whl | Python 3 | none | any | Details for legion_utils-0.6.5-py3-none-any.whl |
Total release size: 138.1 kB
Release files / legion-utils-0.6.5.tar.gz
| Download URL | legion-utils-0.6.5.tar.gz |
|---|---|
| Size | 105.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a4c1889f0b28aa0a6dae838a43796a33b5fe541c9c8a9c2514600e7f6410d0e
|
|
BLAKE2b-256 checksum How to use checksums |
22c059d7415bb65e944c4d79ccc52cac075e2d6c98b77018cc76d09a253b05b4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.11
|
Release files / legion_utils-0.6.5-py3-none-any.whl
| Download URL | legion_utils-0.6.5-py3-none-any.whl |
|---|---|
| Size | 33.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a55665eb3ca6638b3c88cf93bb65be6a5674de43dbf41d59f4184c198cdc3a8d
|
|
BLAKE2b-256 checksum How to use checksums |
a2bc85c9199e506b9cb537a04ec147bc9c0a900d9b2c5254f1481cd395dd5ff6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.11.11
|
Security for legion-utils 0.6.5
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.