_msg: Python Library Logging Facility
_msg, pronounced ‘you-message’, is a module level logging utility intended for libraries, which works just as well for normal logging scenarios. The package name replaces the ‘_’ with a ‘u’ to conform with PEP8 standards.
Installation
pip install umsg
Usage
Class Logging Made Easy
from umsg import LoggingMixin
class MyClass(LoggingMixin):
def __init__(self):
super().__init__(prefix='MyClass')
self.log('Logging initiated', level='debug')
Basic Module / Script Logging Too
import logging
import umsg
umsg.add_handler(logging.StreamHandler())
umsg.log('Good here')
Documentation
Detailed documentation is available on readthedocs.
Metadata
Release files for umsg 1.0.4
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 |
|---|---|---|---|---|
| umsg-1.0.4-py3-none-any.whl | Python 3 | none | any | Details for umsg-1.0.4-py3-none-any.whl |
Release files / umsg-1.0.4-py3-none-any.whl
| Download URL | umsg-1.0.4-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66f51a8b9ae2b4cec8a7f7ad26121640b75fb2423aff7c2f460dc0fdf17f0705
|
|
BLAKE2b-256 checksum How to use checksums |
6bcae02a744119d0f3ba947f5244790baf1190b2dfc8e8009a6e001704fb96d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.42.1 CPython/3.7.6
|
Security for umsg 1.0.4
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.