🌟 Summary (single-line synopsis)
Ultralytics v8.3.248 makes auto-installation more reliable by ensuring uv pip install installs into the currently running Python environment (plus a couple of small quality-of-life fixes) 🧰✅
📊 Key Changes
- Auto-install now targets the active interpreter explicitly (PR #23118) 🧪🎯
check_requirements()runsuv pip installwith--python {sys.executable}so installs go to the right environment (venv/conda/system).- Removed the previous fallback that retried with
uv pip install --system, which could accidentally install into the system Python.
- IMX export: more robust
imxconv-ptdiscovery 🔍📦- Export code now looks for
imxconv-ptin the current Python’sbin/directory first (venv-friendly), then falls back to PATH. - If not found, it raises a clear error with the install hint:
pip install imx500-converter[pt].
- Export code now looks for
- Cleaner plotting code comment (PR #23114) 🧹
- Removed an incorrect TODO that implied a required box-format conversion might be unnecessary (reduces contributor confusion).
- Docker images: quieter logs 🐳🔇
- Adds
TORCH_CPP_LOG_LEVEL=ERRORto suppress noisy PyTorch NNPACK warnings in containers.
- Adds
🎯 Purpose & Impact
- Fewer “installed to the wrong Python” dependency issues 🎯✅
Users in virtualenv/conda, CI, or unusual setups (whereVIRTUAL_ENVisn’t set) should see more predictable installs and fewer broken environments. - More dependable IMX export workflows 🚀
Exporting for IMX (viaimxconv-pt) should “just work” more often inside venvs, and fails faster with an actionable message when the tool isn’t installed. - Improved developer experience 🛠️
Cleaner code signals (plotting) and less log noise (Docker) make debugging and maintenance easier.
What's Changed
- Remove incorrect TODO comment in
plot_imagesby @raimbekovm in #23114 ultralytics 8.3.248Target correct Python env for auto-install by @glenn-jocher in #23118
Full Changelog: v8.3.247...v8.3.248