Ultralytics YOLO
Abstract
π 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() runs uv pip install with --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-pt discovery ππ¦ Export code now looks for imxconv-pt in the current Python's bin/ 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]. 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=ERROR to suppress noisy PyTorch NNPACK warnings in containers. π― Purpose & Impact Fewer "installed to the wrong Python" dependency issues π―β
Users in virtualenv/conda, CI, or unusual setups (where VIRTUAL_ENV isn't set) should see more predictable installs and fewer broken environments. More dependable IMX export workflows π Exporting for IMX (via imxconv-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_images by @raimbekovm in https://github.com/ultralytics/ultralytics/pull/23114 ultralytics 8.3.248 Target correct Python env for auto-install by @glenn-jocher in https://github.com/ultralytics/ultralytics/pull/23118 Full Changelog: https://github.com/ultralytics/ultralytics/compare/v8.3.247...v8.3.248
Publication details
- Journal / source
- Zenodo (CERN European Organization for Nuclear Research)
- Publication date
- 4 January 2026