cham-logging
A small stdlib-only helper for configuring Python logging.
Usage
Call init_logger() once near the start of your process.
import logging
from cham_logging.bootstrap import init_logger
init_logger()
logger = logging.getLogger(__name__)
logger.info("service started")
Environment variables
LOG_LEVEL controls the root logger and handler level.
LOG_LEVEL=DEBUG python -m your_app
If LOG_LEVEL is not set, INFO is used.
LOG_FILE enables an additional UTF-8 file handler.
LOG_FILE=app.log python -m your_app
Both variables can be used together.
LOG_LEVEL=DEBUG LOG_FILE=app.log python -m your_app
Format
Logs use UTC with microsecond precision:
2026-06-14T13:30:00.123456+00:00 - INFO - service started
The timezone is fixed to UTC for now and cannot be configured.
1 maintainer
Metadata
1 maintainer
Release files for cham-logging 0.1.4
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 |
|---|---|---|---|---|
| cham_logging-0.1.4.tar.gz | 4.7 kB | With provenance | Details for cham_logging-0.1.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cham_logging-0.1.4-py3-none-any.whl | Python 3 | none | any | Details for cham_logging-0.1.4-py3-none-any.whl |
Total release size: 7.9 kB
Release files / cham_logging-0.1.4.tar.gz
| Download URL | cham_logging-0.1.4.tar.gz |
|---|---|
| Size | 4.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3fafb99fb6f9f617e0c3e5f0de9e32fb24cb57c87aec16993d7a064ee25ec73b
|
|
BLAKE2b-256 checksum How to use checksums |
c70b131d6cdc1a41cd781b7aab936da4bf5253e92d6d0c28da0aa1ba542343b1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logRelease files / cham_logging-0.1.4-py3-none-any.whl
| Download URL | cham_logging-0.1.4-py3-none-any.whl |
|---|---|
| Size | 3.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc1ee44a39e49e0e370ac701c66117e0779fde62deb6c4edc3e9a43f99755b12
|
|
BLAKE2b-256 checksum How to use checksums |
05c5bb3690ab3c380a2f29060ee3955d4a9909248585e1517fca27c4f643b3cb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logSecurity for cham-logging 0.1.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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for cham_logging-0.1.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 30, 2026.
Transparency logA 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.
