uv

Raised as a usability problem by 34 people on Hacker News over 3 years (2024–2026), in 19 threads.

People raised many different problems with uv, but no single problem has yet been raised by 3 people in 3 different months and threads.

Unreviewed issues were grouped by machine: Claude Haiku labelled each comment as a usability complaint, named what it's about and summed up the problem in a line, and a small model grouped similar problems. Nobody has checked them by hand. Expect mistakes.

The newest 39 complaints

Two commands show outdated packages with very different output, which is confusing2026-05-22
Users run uv pip install on pyproject.toml, bypassing uv.lock and getting unlocked dependencies2026-05-22
Cannot leave one dependency unlocked while locking the others, forcing all-or-nothing locking2026-05-22
Getting a script to install, skip, or update itself correctly was surprisingly tricky and slow2026-05-22
Dependency upgrades are painful; needed commands hidden under uv pip subcommand2026-05-22
Commander finds the uv command line interface cumbersome to use2026-05-21
Forces virtual environments into a single project directory, causing inconvenient duplication of libraries2026-03-23
Puts the venv inside the project, cluttering the workspace and forcing re-bootstrap after git clean2026-03-23
Install results depend on the order packages are passed2025-12-30
Documentation barely exists, making the build tool hard to learn2025-12-17
Clever automatic tool behaviour overrides settings, forcing users to second-guess and work around it2025-10-30
Pip-style install leaves projects working only on one machine, inviting confusion2025-10-30
Home page opens with a long list of technical details, confusing newcomers2025-10-29
Must retype the package list every time to start a REPL with packages2025-10-29
Triggers unwanted Python downloads when using other features, bypassing the system package manager2025-10-14
Defaults to newest Python, which breaks programs needing older versions2025-10-14
Documentation lists many options without recommending one clear workflow, so users are confused2025-08-28
Commenter couldn't understand uv workspaces from the docs after an hour2025-08-28
Re-downloads huge dependencies per clone and duplicates them on disk across projects2025-08-27
Unclear which pyproject.toml section configures formatting, and which takes priority2025-08-22
Help text is too terse, so users skip exploring commands and miss capabilities2025-08-22
Documentation is rough around the edges2025-06-24
Guides are buried; must read bullets and click several times to find them2025-06-23
Hard to understand why things don't work or make sense when running with uvx2025-06-23
Having to type the extra --system flag makes commands longer and raises typo risk2025-06-23
Unclear how to run projects locally, forcing trial-and-error with commands and missing references2025-06-23
Users must read the README to learn how to run projects; import paths not handled2025-06-23
Uv sync forgets applied extras, so uv add reinstalls the wrong torch build2025-03-17
Uv sync silently undoes previously selected extras, forcing constant manual tracking2025-03-13
Uv add uninstalls and reinstalls packages, forcing manual --extra resyncs on each machine2025-03-13
Interactive sessions with uv environments in VS Code under WSL start up very slowly2025-03-13
Found uv too hard to use, so the commenter went back to venv2025-03-06
Commenter finds uv's design neither intuitive nor usable2025-02-19
Authors must learn and switch between separate build backend docs and configs2025-02-19
NVIDIA packages need a pip-breaking helper package to install, and uv refuses it2025-02-19
Dislikes the UI where every command is prefixed with the tool suite name2025-01-13
Installing PyTorch with an unsupported Python version gave very confusing errors2024-11-19
Runs into weird issues when the underlying Python installation is bad2024-10-30
Can't find information on how conda works as a dependency source2024-08-29