The repository or configuration that created this release differ from a previous release. View details.
Atlogger
Python decorator to log artifacts with mlflow, wandb, rerun, tensorboard, etc...
Inspired by many talks with colleagues, frustrating nights and the python logging documentation I am attempting to develop a module to streamline the proper logging for model training and comparisons
How to use
export WANDB_API_KEY="wandb_key"
# main.py
from atlogger import logger, WandbHandler
logger.addHandler(
WandbHandler(
project="your_project_name",
config={"config":True},
level="DEBUG"
)
)
# lossFunc.py
from atlogger import log
@log
loss(x1,x2):
return abs(x1 - x2)
@log("euclidean distance")
calc_distance(x1,x2):
return sqrt(x1**2 - x2**2)
you can also use many other functionalities from pythons logging from the standard library as well as the many handlers we made to integrate seamlessly with diverse logging, profiling and code tracking libraries.
for more information head over to the documentation
Principles
Ideally this project will have the following principles:
- Non-intrusive:
- Snippets used for logging shouldn't be in the middle of the code. Anyone should be able to import code from one project to another without having to go through and delete or change lines throughout the functions.
- Modular:
- Added visualizations should be easy to add and be defined on their own and reused anywhere needed. enabling the user to use only the packages they already have without being locked behind a stack of dependencies
- Explicit:
- Logging shall not happen under the hood. you should be able to define and easily recognize when information is being logged but also have sensible defaults as not to loose important information that is constantly ignored (i.e. logging hardware load during ML models training)
- Adaptable:
- I want to be able to use this tool for logging diverse kinds of code and easily change between them:
- Ml training
- Compression algorithms
- async algorithms
- profiling algorithm duration
- reinforcement learning / robotics
- I want to be able to use this tool for logging diverse kinds of code and easily change between them:
Known bugs
- running logger inside jupyter notebook ony works for one cell
- config from file is not logging with proper log levels
- wandb handler might not be filtering by log level
Current Goals
- Add a basic implementation of mlflow, rerun, profiling
- Only uses packages you have installed
- Enable choice of what happens if logging fail: break, or ignore
- Continue experiments
- Log artifacts like images or models
- Pass custom logger and custom formatter per call
Metadata
Release files for atlogger 0.2.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Change of provenance
The repository or configuration that created these release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| atlogger-0.2.3.tar.gz | 6.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| atlogger-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.7 kB
Release files / atlogger-0.2.3.tar.gz
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | atlogger-0.2.3.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a5f3d30df164db142d9be233dbd09366c3a74d5094c9a4615742acb4695d27c3
|
|
BLAKE2b-256 checksum How to use checksums |
c8cec9875df5982d30cb84a072b3fc078ddb3756d4ca82e2c72fdcab5401f49e
|
| 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 23, 2026.
Transparency logRelease files / atlogger-0.2.3-py3-none-any.whl
Change of provenance
This file belongs to a release with changed provenance: the repository or configuration that created the release files differ from that of a previous release.
We recommend inspecting the repository and configuration before proceeding. View details.
| Download URL | atlogger-0.2.3-py3-none-any.whl |
|---|---|
| Size | 8.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e216bf390b6b94d5b50438d38a8c94d52bc41a38a70c28c8b0f62c57f9f5e387
|
|
BLAKE2b-256 checksum How to use checksums |
083e8c59eba49f1b1763be757cbb91b36115d842d18028d6f53df56f49e4c8f6
|
| 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 23, 2026.
Transparency logSecurity for atlogger 0.2.3
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.
Change of provenance
The repository that created this release differs from a previous release.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Repository
- Removed 0.2.1 GitHub: drawnator/atlogger
- Added 0.2.3 GitHub: drawnator/Atlogger
Attestation for atlogger-0.2.3.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 23, 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.