Log all calls to a module
Dependencies
structlog
Features
Log all calls to a module
Example
>>> from logmod import logmod
>>> import secrets
>>> logmod(secrets)
>>>
>>> secret.token_hex(5)
logmod: call to secret.token_hex with (5,) {}
'd34eb399f8'Results in:
2018-01-09 01:04.15 coolname -> secrets.token_hex at example.py:8 args=(5,) caller=coolname callsite={'filename': 'example.py', 'lineno': 8} func=token_hex kwargs={} mod=secrets
2018-01-09 01:04.15 token_hex -> secrets.token_bytes at /usr/lib/python3.6/secrets.py:58 args=(5,) caller=token_hex callsite={'filename': '/usr/lib/python3.6/secrets.py', 'lineno': 58} func=token_bytes kwargs={} mod=secrets
Hello, f717fd2370
2018-01-09 01:04.15 <module> -> random at example.py:12 args=() caller=<module> callsite={'filename': 'example.py', 'lineno': 12} func=random kwargs={} mod=None
0.468991586044451241 maintainer
Metadata
1 maintainer
Release files for logmod 0.1
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 |
|---|---|---|---|---|
| logmod-0.1.tar.gz | 2.0 kB | Without provenance | Details for logmod-0.1.tar.gz |
Release files / logmod-0.1.tar.gz
| Download URL | logmod-0.1.tar.gz |
|---|---|
| Size | 2.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ee75bbf91da20b1b98f2c602fb3dff64594969c3bcb8ba6da9f16951e0b78b8
|
|
BLAKE2b-256 checksum How to use checksums |
9a384cc48177647fbc682e1662b940422df5d308cec0dac489ce74c9e7b6945a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for logmod 0.1
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.
