deep-learning-wandb
Public Weights & Biases integration layer for deep-learning-core.
deep-learning-wandb adds a W&B callback and scaffold integration on top of
deep-learning-core. It keeps tracking-specific logic outside the core
framework while still allowing users to install it through
deep-learning-core[wandb].
Current release: deep-learning-wandb==0.0.16.
Requires deep-learning-core>=0.1.4,<0.2.
What's New in 0.0.16?
- the core compatibility floor is now
deep-learning-core>=0.1.4,<0.2, keeping W&B installations aligned with the coordinated package release - W&B 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[wandb]"
Install the package directly:
pip install deep-learning-wandb
Install in a uv project:
uv add "deep-learning-core[wandb]"
Scope
- W&B callback registration for
deep-learning-core - Experiment scaffold integration through
dl-init --with-wandb - W&B-ready config defaults for generated experiment repositories
Out Of Scope
- Generic trainer, dataset, and metric abstractions
- Azure execution or storage logic
- Company-specific W&B entities, projects, or secrets
Quick Start
Install it through the deep-learning-core extra:
uv add "deep-learning-core[wandb]"
Then scaffold a W&B-ready experiment repository:
uv run dl-init --name my-exp --with-wandb
The generated experiment package will import dl_wandb automatically so the
wandb callback registers at runtime.
It also ignores .env, other local environment files, and wandb/, while
keeping .env.example available as the credential template.
Concrete experiment flow:
uv init
uv add deep-learning-wandb
uv run dl-init --root-dir . --with-wandb
uv run dl-run --config configs/base.yaml
uv run dl-sweep experiments/lr_sweep.yaml
The W&B project defaults to the repository root name unless
tracking.experiment_name overrides it. The sweep file name becomes the W&B
run group unless tracking.sweep_name overrides it.
What You Get
- the
wandbcallback for local training runs - epoch, RL episode, algorithm-update, and evaluation metric logging, with RL
series indexed by the environment-transition
global_step dl-init --with-wandbscaffold support- generated W&B callback defaults and
.env.example
Companion Packages
Documentation
License
MIT. See LICENSE.
Release files for deep-learning-wandb 0.0.16
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_wandb-0.0.16.tar.gz | 149.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deep_learning_wandb-0.0.16-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 161.7 kB
Release files / deep_learning_wandb-0.0.16.tar.gz
| Download URL | deep_learning_wandb-0.0.16.tar.gz |
|---|---|
| Size | 149.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e8a551f361377650466e2151e8c4f49bc71bc7843770b4843d5a8c9025bb338e
|
|
BLAKE2b-256 checksum How to use checksums |
9285e8a1753404d6c8047fa0c3adebdd3dfd584a513f52d2eba7c6d92e27dfe9
|
| 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_wandb-0.0.16-py3-none-any.whl
| Download URL | deep_learning_wandb-0.0.16-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8b7413d1faea9fa97b64169fe4780be6c2c37a314810330a3e9c3bc0eff992bc
|
|
BLAKE2b-256 checksum How to use checksums |
4a9f9e323ae6b20dd34155995903fc496ba900abdbd6252e481aedde5e44156e
|
| 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