Utilities for Legion Reporters and Monitors
Project description
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
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
File details
Details for the file legion-utils-0.4.2.tar.gz
.
File metadata
- Download URL: legion-utils-0.4.2.tar.gz
- Upload date:
- Size: 101.3 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.1.1 CPython/3.11.9
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 977d3645f2b97f7f88187506f53189f552c7c0f9f06c6e2c91e79cd195c43c73 |
|
MD5 | 1a0d2f3d49e710e7b23dd37e0b4446d9 |
|
BLAKE2b-256 | 18797a901adb8f846de5ab8193b0479495cf0ea015ef2c813ebe7f0aa321fbfa |
File details
Details for the file legion_utils-0.4.2-py3-none-any.whl
.
File metadata
- Download URL: legion_utils-0.4.2-py3-none-any.whl
- Upload date:
- Size: 28.6 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/5.1.1 CPython/3.11.9
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | 1feb0f57fd90d77a0ba31d71f7945fcf0fa2e792aeaf89bff053055649e2f4b6 |
|
MD5 | 07ae43ed96ea0e0b691559536a40afa7 |
|
BLAKE2b-256 | 8bd687f6f0db045be4f389fed8fb771fe5f50f9ca83501d30cee04b8c7358165 |