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.16. Requires deep-learning-core>=0.1.8,<0.2.

What's New in 0.0.16?

  • local MLflow sweep runs nest under their parent, and invalid scalar metrics are omitted from logging
  • runtime extension registration and scaffold setup work with dl-core 0.1.8
  • the development PyTorch requirement is torch>2.3 without an upper cap

Previous versions are recorded in the release history.

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
  • terminal run statuses mapped from the trainer lifecycle: FINISHED for completed runs, FAILED for failures, and KILLED for interruptions
  • dl-init --with-mlflow scaffold support
  • local ./mlruns tracking defaults for generated experiment repositories
  • automatic upload of epoch_<n>/, final/, and config.yaml artifacts
  • runtime registration through dl-core's installed-extension entry points

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

Companion Packages

Docs

License

MIT. See LICENSE.

Release files for deep-learning-mlflow 0.0.16

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.16
File Size Uploaded
deep_learning_mlflow-0.0.16.tar.gz 230.6 kB Details

Built distribution (wheel)

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

Total release size: 243.5 kB

Release files / deep_learning_mlflow-0.0.16.tar.gz

Download URL deep_learning_mlflow-0.0.16.tar.gz
Size 230.6 kB
Tags Source
SHA-256 checksum
How to use checksums
d16eb3ee432c74277e517625270c7eb8a784f9d7c6c807f1b23cf52bf68851ab
BLAKE2b-256 checksum
How to use checksums
a0d4124d3c6a98b3e0a4a9f0b4547a2872638451a46fb4e308f4d0f9bc22ac1c
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 Sep 24, 2026.

Transparency log

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

Download URL deep_learning_mlflow-0.0.16-py3-none-any.whl
Size 13.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9f025eefd52c59ce810e8d25923dc2353c1f59716994cd49e17240f709edf325
BLAKE2b-256 checksum
How to use checksums
370bea76c1fdba81bf69d72fa8d63652c37d7c97af2580d14fd59d5294623c2c
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 Sep 24, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.0.16 This release

2 release files

0.0.15

2 release files

0.0.14

2 release files

0.0.13

2 release files

0.0.12

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