UV Migration
summary
Migrates many notebook images from Pipenv to UV by converting Pipenv locks into pyproject.toml, changing Dockerfiles to pip-install UV, and adding GitHub Actions that auto-generate requirements.txt and lock files. Uses UV features like groups and sources plus dependency metadata and environment markers to support conflicting package versions and multi‑Python (3.11→3.12) builds. Builds and benchmarks show large GPU stacks (PyTorch/TensorFlow) and lock times improve — 17 minutes → 3 minutes — while image size and overall build time are tracked.
AI-written summary · about
related talks
27muv: Ultimate Victory over Installation and Dependency Chaos
28mBeyond the Benchmark: Why the “Best” Python Dependency Manager Might Not Be Best for You
33mThe past, present, and future of virtual environments
28mBreaking Free from Virtual Environments Python's New Paradigm for 2026
20mHow I got unstuck with Python
39mPeeking under the hood of uv run
36mPipenv: The Future of Python Dependency Management
16mUsing Python to Streamline Asset Workflows