Skip to main content

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


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

legion-utils-0.6.4.tar.gz (105.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

legion_utils-0.6.4-py3-none-any.whl (32.9 kB view details)

Uploaded Python 3

File details

Details for the file legion-utils-0.6.4.tar.gz.

File metadata

  • Download URL: legion-utils-0.6.4.tar.gz
  • Upload date:
  • Size: 105.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.1.1 CPython/3.11.11

File hashes

Hashes for legion-utils-0.6.4.tar.gz
Algorithm Hash digest
SHA256 e4b94835e70ca0373f2b7aa10e6d603f8f5c5185eb7387229d4e2b4d55cea8c2
MD5 f3b60608acf5995b4a23426994c52786
BLAKE2b-256 2ed70b21d079f72cfe4571bf59f85e1301b9a0e9fc23377507491f30db222b43

See more details on using hashes here.

File details

Details for the file legion_utils-0.6.4-py3-none-any.whl.

File metadata

  • Download URL: legion_utils-0.6.4-py3-none-any.whl
  • Upload date:
  • Size: 32.9 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.1.1 CPython/3.11.11

File hashes

Hashes for legion_utils-0.6.4-py3-none-any.whl
Algorithm Hash digest
SHA256 18ca07303ebcd318bca88137fd5bcb0e756e74741210dc60ebf8eb7f382fdeaa
MD5 703f751f127160d2e7464703b0141a20
BLAKE2b-256 9ff326189db10576e443c91957f78487a75d431cc7c443ef5c21b4a6ed948209

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page