Skip to main content

atlogger

Python decorator to log artifacts with mlflow, wandb, rerun, tensorboard, etc...

Inspired by the 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 ATLOGGER, WandbHandler

ATLOGGER.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)

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.
  • 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:
      1. Ml training
      2. Compression algorithms
      3. async algorithms

Known bugs

  • if you use the decorator as @log instead of @log()the function will be passed as the variable "names" for some reason
  • Curently not accepting multiple outputs from functions
  • Creating the wandbhandler within config file for some reason does not get to this part of the loginwandb: Currently logged in as: <usr> to https://api.wandb.ai. Use `wandb login --relogin` to force relogin
  • running logger inside jupyter notebook ony works for one cell

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
  • add custom ENUMs instead of DEBUG, WARN, INFO...

Metadata

Release files for atlogger 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for atlogger 0.1.0
File Size Uploaded Provenance
atlogger-0.1.0.tar.gz 6.6 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for atlogger 0.1.0
File Interpreter ABI Platform
atlogger-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 13.7 kB

Release files / atlogger-0.1.0.tar.gz

Download URL atlogger-0.1.0.tar.gz
Size 6.6 kB
Tags Source
SHA-256 checksum
How to use checksums
b0aa05bbe1b60cee149a4a2a26354a85da31370039eb6a84e1de1df2f6f1c23c
BLAKE2b-256 checksum
How to use checksums
c174866946bdb00d91054a70ef40c1ecbc013d9e768f50fc5d83c0276abcb283
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 5, 2026.

Transparency log

Release files / atlogger-0.1.0-py3-none-any.whl

Download URL atlogger-0.1.0-py3-none-any.whl
Size 7.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
d2eedc1ce3211b18508a3d149f70dd6911a6587d7488a6d8bcd7e3321265acc8
BLAKE2b-256 checksum
How to use checksums
83d3a62a78eb5a0eed585a7e78c2d0499fe317abc1310e2989c7f3f0e0bd225e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 5, 2026.

Transparency log

Security for atlogger 0.1.0

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

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for atlogger-0.1.0.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 5, 2026.

Transparency log

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page