[](https://travis-ci.org/Python-Logging-For-Human/ezlogging)
# ezlogging
ezlogging
https://paper.dropbox.com/doc/Logging-For-Human-0hgb3uUWhAgi4kJcU3r5X
# test py.test –capture=sys
Metadata
Release files for lazy_logger 0.1.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 | |
|---|---|---|---|---|
| lazy_logger-0.1.1.tar.gz | 2.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| lazy_logger-0.1.1.macosx-10.6-intel.tar.gz | Details |
Total release size: 6.3 kB
Release files / lazy_logger-0.1.1.tar.gz
| Download URL | lazy_logger-0.1.1.tar.gz |
|---|---|
| Size | 2.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b2eb85b99008a5298d3745a059c9c7378a0b4fc1cb19d3e9ba06d6f48997a082
|
|
BLAKE2b-256 checksum How to use checksums |
93489cfa9d29caf089a456b3066896371aa14ffc61338ffdd5aa60979a60680b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / lazy_logger-0.1.1.macosx-10.6-intel.tar.gz
| Download URL | lazy_logger-0.1.1.macosx-10.6-intel.tar.gz |
|---|---|
| Size | 4.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a107bafe5ec0f731cf5bc1d58118a7714569ba1085bf2cfc8dee1f64d47b4943
|
|
BLAKE2b-256 checksum How to use checksums |
ad4043a0da93a68f3a30ac1e94e3b1b845e2c7db78b46e0532f3b2828f3d325e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for lazy_logger 0.1.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.