uv

13 engineers on Hacker News describe using uv first-hand: 9 endorse it, 1 regret it, 1 are mixed.

82%trust
13first-hand users
9in production
endorse 9mixed 1regret 1uses, no opinion

“We switched to using it for distribution of our Python-based tools because it makes it very convenient to install directly from a git repository”

endorse · production · dboreham · 2026-08-31 · source ↗ · wrong label?

“I've been using it for so long now that I recently couldn't remember how to use Python without it”

endorse · production · Quothling · 2025-12-30 · source ↗ · wrong label?

“IMO uv sync and uv run have no place in production. I do not want my server to resolve dependencies or create environments at all”

mixed · production · amluto · 2025-12-18 · source ↗ · wrong label?

“uv is a revolution in every possible positive sense of the word in the Python world and I've been here since 1.5.”

endorse · personal · baq · 2025-12-02 · source ↗ · wrong label?

“I tried 2CPU/8GB runners but it still OOMed occasionally so didn't seem worth using up those resources for the normal case.”

regret · production · alisonatwork · 2025-08-14 · source ↗ · wrong label?

“One life-changing thing I've been using `uv` for”

endorse · personal · danudey · 2025-08-13 · source ↗ · wrong label?

“if we already have uv, could we get away without docker? uv sync can give an experience almost akin to static compiled binaries”

endorse · production · CraigJPerry · 2025-07-16 · source ↗ · wrong label?

“We run internal benchmarks of our custom container image builder and in the 'install torch' benchmark the p50 time saved when using `uv` is 25 seconds!”

endorse · production · thundergolfer · 2024-11-20 · source ↗ · wrong label?

“moving from poetry to uv was rock solid. No issues and it just worked. I was surprised.”

endorse · production · colemannerd · 2024-10-30 · source ↗ · wrong label?

“I like using UV, it is painless, a proper in-place replacements and blazingly fast.”

endorse · personal · screye · 2024-07-02 · source ↗ · wrong label?

“My work saw a 5x speedup (~2min to ~20s) with a cold cache and like 200-500x (~20s to <0.1s) with a hot cache in our CI pipelines when we switched to uv.”

endorse · production · otonnesen · 2024-06-04 · source ↗ · wrong label?

“Use the fixed pipx to update uv (although I guess the uv self-update should work even for a pipx-installed copy?)”

neutral · personal · zahlman · 2026-10-25 · source ↗ · wrong label?

“we replaced all our of 'pip' with 'uv pip'. Shit goes south and we simply change it back at the cost of speed.”

neutral · production · walthamstow · 2025-06-24 · source ↗ · wrong label?