This python library provides logging utilities we use when building micro-services.
Hacking Notes:
To hack on the library, create a python3 virtual environment with the development dependencies getting the project pip-cache:
$ make bootstrap
possibly:
$ . env/bin/activate
To run the tests:
$ make test
Dependencies:
setup.py does not list any install-time dependencies, and users of this library must ensure they have the required dependencies configured.
Release files for uservice-logging 0.10.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| uservice_logging-0.10.2-py3-none-any.whl | Python 3 | none | any | Details for uservice_logging-0.10.2-py3-none-any.whl |
Release files / uservice_logging-0.10.2-py3-none-any.whl
| Download URL | uservice_logging-0.10.2-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6045f76c11c2c524fcaf5238df6c53f95932c2313f598a60fc2adcb7f7861b0a
|
|
BLAKE2b-256 checksum How to use checksums |
b4069c945200a5faad30ae65e51278d446fc08315eb173ef9830a015ae640b5a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for uservice-logging 0.10.2
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.
