Skip to main content

deep-learning-mlflow

Local MLflow integration layer for deep-learning-core.

deep-learning-mlflow adds local MLflow tracking on top of deep-learning-core without Azure dependencies. It is the public MLflow variant behind deep-learning-core[mlflow].

Current release: deep-learning-mlflow==0.0.12. Requires deep-learning-core>=0.0.26,<0.1.

What's New in 0.0.12?

  • RL training episodes, algorithm updates, and aggregate evaluations are logged alongside the existing supervised epoch metrics
  • evaluation episodes remain separate from training-episode metric series
  • a tracking URI supplied through the top-level tracking configuration now takes precedence over the callback fallback
  • generated repositories depend directly on deep-learning-mlflow and ignore the local mlruns/ directory

Install

Install from PyPI through the core extra:

pip install "deep-learning-core[mlflow]"

Install the package directly:

pip install deep-learning-mlflow

Install in a uv project:

uv add "deep-learning-core[mlflow]"

Quick Start

uv init
uv add deep-learning-mlflow
uv run dl-init --root-dir . --with-mlflow
uv run dl-run --config configs/base.yaml
uv run dl-sweep experiments/lr_sweep.yaml

The scaffold points MLflow at a local ./mlruns directory by default. Generated repositories ignore mlruns/ so local tracking data is not accidentally committed. Tracker experiment naming defaults to the repository root name unless tracking.experiment_name overrides it. Run artifacts are uploaded from config.yaml, per-epoch epoch_<n>/ directories after checkpointing, and final/ at the end of training.

Concrete local tracking flow:

uv run dl-init --root-dir . --with-mlflow
uv run dl-run --config configs/base.yaml
uv run dl-analyze --sweep experiments/lr_sweep.yaml

What You Get

  • the mlflow callback for local training runs
  • epoch, RL episode, algorithm-update, and evaluation metric logging
  • dl-init --with-mlflow scaffold support
  • local ./mlruns tracking defaults for generated experiment repositories
  • automatic upload of epoch_<n>/, final/, and config.yaml artifacts

Azure-backed MLflow wiring remains part of dl-azure.

Companion Packages

Docs

License

MIT. See LICENSE.

Release files for deep-learning-mlflow 0.0.12

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

Source distribution (sdist)

Source distribution for deep-learning-mlflow 0.0.12
File Size Uploaded
deep_learning_mlflow-0.0.12.tar.gz 229.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for deep-learning-mlflow 0.0.12
File Interpreter ABI Platform
deep_learning_mlflow-0.0.12-py3-none-any.whl Python 3 none any Details

Total release size: 242.4 kB

Release files / deep_learning_mlflow-0.0.12.tar.gz

Download URL deep_learning_mlflow-0.0.12.tar.gz
Size 229.9 kB
Tags Source
SHA-256 checksum
How to use checksums
9ee26281e4249af6cb39f88dd4a2cdc291525a43b627421268a21578825e85b5
BLAKE2b-256 checksum
How to use checksums
541910e0dc4eb546e0bd69160cf8159ef45dae63615f21761597bc759ce42cf4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 19, 2026.

Transparency log

Release files / deep_learning_mlflow-0.0.12-py3-none-any.whl

Download URL deep_learning_mlflow-0.0.12-py3-none-any.whl
Size 12.6 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b88e9de2848fb75b458b19b0a030a0985d789e47dbd68c0494e76749054ed9c0
BLAKE2b-256 checksum
How to use checksums
42ca88f7c9310c410d3f6e1d6b0a2849e14773c0146523f7bebf2a5a83574f1f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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 Jul 19, 2026.

Transparency log

Release history Release notifications | RSS feed

0.0.15

2 release files

0.0.14

2 release files

0.0.13

2 release files

This release

0.0.12 This release

2 release files

0.0.11

2 release files

0.0.10

2 release files

0.0.9

2 release files

0.0.8

2 release files

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