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.15.
Requires deep-learning-core>=0.1.4,<0.2.
What's New in 0.0.15?
- the core compatibility floor is now
deep-learning-core>=0.1.4,<0.2, keeping MLflow installations aligned with the coordinated package release - MLflow callbacks, trackers, metric sources, and scaffold behavior remain unchanged while new trainer and tar-dataset functionality comes from core
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
mlflowcallback for local training runs - epoch, RL episode, algorithm-update, and evaluation metric logging
dl-init --with-mlflowscaffold support- local
./mlrunstracking defaults for generated experiment repositories - automatic upload of
epoch_<n>/,final/, andconfig.yamlartifacts
Azure-backed MLflow wiring remains part of dl-azure.
Companion Packages
Docs
License
MIT. See LICENSE.
Release files for deep-learning-mlflow 0.0.15
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| deep_learning_mlflow-0.0.15.tar.gz | 227.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deep_learning_mlflow-0.0.15-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 240.1 kB
Release files / deep_learning_mlflow-0.0.15.tar.gz
| Download URL | deep_learning_mlflow-0.0.15.tar.gz |
|---|---|
| Size | 227.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1149afbdc3d8d3f7ecd60990c0d64e84f75adcaa5ff7137314f9a48dfabbcf75
|
|
BLAKE2b-256 checksum How to use checksums |
d4e15f3ecff35b7d29a7fe2fe1313776564755adbc87d0a6b0590ea676538d91
|
| 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 Aug 14, 2026.
Transparency logRelease files / deep_learning_mlflow-0.0.15-py3-none-any.whl
| Download URL | deep_learning_mlflow-0.0.15-py3-none-any.whl |
|---|---|
| Size | 12.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c3f3e8a9f304eb72e3627350c1bda5603365bcd81f67696782cfb102771ec172
|
|
BLAKE2b-256 checksum How to use checksums |
f9000aa4e721fccbc97253140a6dd6157466d29e73b8c0df85b704008a3efc34
|
| 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 Aug 14, 2026.
Transparency log