🚂 chugchug
Next-generation progress bars for Python. Event-driven, multiprocessing-safe, pipeline-aware.
Zero dependencies. Beautiful gradients. Smart ETA. Just works.
Why chugchug?
| Feature | tqdm | Rich | chugchug 🚂 |
|---|---|---|---|
| Zero dependencies | yes | no | yes |
| Event-driven architecture | no | no | yes |
| Multiprocessing (spawn-safe) | no | no | yes |
| Pipeline/DAG progress | no | no | yes |
| "Why is it slow?" diagnostics | no | no | yes |
| Beautiful gradient bars | no | yes | yes |
| Smart ETA (regression + ensemble) | no | no | yes |
| ML metrics (loss, lr, auto-colored) | no | no | yes |
| Notebook support (HTML/CSS bars) | partial | yes | yes |
| JSON/LOG/TTY output modes | partial | no | yes |
| Smart generator wrapping | no | no | yes |
| tqdm drop-in compatible | - | no | yes |
🚀 Install
pip install chugchug
🚂 Quick Start
from chugchug import chug
for item in chug(range(100), desc="Working"):
process(item)
That's it. One import, one line. Gradient bar, smart ETA, speed tracking — all automatic.
🎨 Gradients
14 built-in gradient presets:
chug(data, gradient="ocean") # blue → cyan (default)
chug(data, gradient="fire") # red → gold
chug(data, gradient="rainbow") # full spectrum
chug(data, gradient="aurora") # northern lights
chug(data, gradient="candy") # pink → purple → cyan → green
chug(data, gradient="neon") # magenta → cyan → yellow
# + forest, purple, cyber, mono, heatmap, sunset, matrix, ice
Custom gradients:
from chugchug import register_gradient, register_multi_gradient
register_gradient("coral", (255, 94, 77), (255, 195, 113))
register_multi_gradient("vaporwave", [
(255, 0, 128), (128, 0, 255), (0, 200, 255), (0, 255, 180),
])
🧠 ML Training
from chugchug import Chug
b = Chug(total=num_steps, desc="Training", gradient="fire", unit="step")
for step in range(num_steps):
loss, acc = train_step()
b.set_metrics(loss=f"{loss:.4f}", acc=f"{acc:.1%}")
b.update()
b.close()
Metrics like loss auto-color green when improving, red when worsening.
🔄 tqdm Drop-in
# Before
from tqdm import tqdm
# After — just change the import
from chugchug.compat import tqdm, trange
🪄 Smart Generators
tqdm shows 0it [00:00, ?it/s] for map(), enumerate(), generator expressions. chugchug extracts the total automatically:
chug(map(fn, data)) # detects total from data
chug(enumerate(data)) # works too
chug(x**2 for x in data) # even generator expressions
📓 Notebooks
Auto-detected in Jupyter — renders as HTML/CSS gradient bars:
for item in chug(range(100), desc="Training"):
process(item)
Or force it: chug(data, output="notebook").
🏗️ Pipelines
from chugchug._pipeline import Pipeline
pipe = Pipeline("ETL")
pipe.add_stage("extract", total=1000, desc="Extracting")
pipe.add_stage("transform", total=1000, depends_on=["extract"])
pipe.add_stage("load", total=1000, depends_on=["transform"])
with pipe:
# stages run with progress tracking, bottleneck detection
...
⚡ Multiprocessing
Spawn-safe. No shared memory. Just works.
from chugchug._mp import MPContext
from concurrent.futures import ProcessPoolExecutor
with MPContext() as ctx:
with ProcessPoolExecutor(max_workers=4) as pool:
for i in range(4):
t = ctx.tracker(f"worker-{i}", total=100)
pool.submit(work, t)
🔍 Diagnostics
for item in Chug(range(10000), desc="Analysis", diagnostics=True):
process(item)
# [chugchug diagnostic] CPU-BOUND: Consider multiprocessing...
📊 Output Modes
chug(data, output="tty") # terminal with gradients (default)
chug(data, output="notebook") # HTML/CSS bars for Jupyter
chug(data, output="json") # structured JSON lines for CI/CD
chug(data, output="log") # human-readable log lines
chug(data, output="silent") # tracking only, no output
🏛️ Architecture
chugchug separates tracking from rendering:
- Trackers produce
ProgressEventobjects (immutable, picklable) - Registry dispatches events to handlers (lock-free hot path)
- Handlers render output (TTY, Notebook, JSON, LOG, custom)
CLI
cat urls.txt | python -m chugchug pipe --desc "Downloading"
python -m chugchug watch progress.jsonl
python -m chugchug replay recording.jsonl --speed 2.0
License
MIT
Metadata
Release files for chugchug 0.1.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| chugchug-0.1.3.tar.gz | 50.5 kB | Without provenance | Details for chugchug-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| chugchug-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for chugchug-0.1.3-py3-none-any.whl |
Total release size: 99.3 kB
Release files / chugchug-0.1.3.tar.gz
| Download URL | chugchug-0.1.3.tar.gz |
|---|---|
| Size | 50.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
170a1997ad4e71159156f129231861edd17ea4f10baa299ffd686e728a4bbe44
|
|
BLAKE2b-256 checksum How to use checksums |
ed9ea06f5843f91b57e4b3d19c80ef3ba51482c68ee456d94fe4723fca5feac0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / chugchug-0.1.3-py3-none-any.whl
| Download URL | chugchug-0.1.3-py3-none-any.whl |
|---|---|
| Size | 48.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7fa1f51df72bf03390c45fae9e2ed6caf216708a33efb1a07d3e7cfd1f931f7c
|
|
BLAKE2b-256 checksum How to use checksums |
5b7ed0b7ebab8e25d032a993ab1bb7232c39d2122f434bec8a627ad43006e6f8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for chugchug 0.1.3
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.