Python developers using uv can't cap how much disk its cache uses.
Python developers and CI runners using uv
Where it stands
- Sourced (done)
- Kit (done)
- Wanted (next)
- Building
- Solved
How this problem came to be
- Found2 sourcesgithub.com/astral-sh, docs.astral.sh
- Quoted3 claimseach checked against its page
- BriefWrittenand what solved looks like
- Market1 signals56 reactions on the issue
- Kit5 steps20 tools · 6 routes
- People0 want0 live it · 0 would test
The problem, broken down
- Who it hurts
- Developers and CI administrators who use uv, a widely used Python package manager.
- The moment
- When a laptop or build server runs out of disk and the uv cache turns out to be tens of gigabytes.
- What people do today
- People run uv cache clean or uv cache prune by hand or from their own scripts.
- Why it's unsolved
- The issue is labelled ‘needs design’; evicting entries safely while other uv processes use the cache is not trivial.
- What solved looks like
- A design note and prototype for an opt-in size limit that removes least-recently-used entries after an install, without breaking other uv processes running at the same time. Tested by filling a cache past the limit and checking it ends under the limit while recent packages still install offline.
Evidence
Every claim is tied to the source it comes from- 1uv has no setting to limit its cache size; the issue opener saw caches grow to about 40 GB on self-hosted CI runners.
- 2Commenters report pruning 60 GB, a 99 GB cache that crashed a laptop, and about 300 GB found only after disk-space warnings.
- 3uv's documentation describes manual commands, uv cache clean and uv cache prune, for clearing the cache.
Builders still need to know
Written from the cited sources. Anything they don't say is left as a question, not a guess.
Sources
From a public page with a citation.
What the source says, in short
uv has no setting to limit its cache size; the issue opener saw caches grow to about 40 GB on self-hosted CI runners. Commenters report pruning 60 GB, a 99 GB cache that crashed a laptop, and about 300 GB found only after disk-space warnings. uv's documentation describes manual commands, uv cache clean and uv cache prune, for clearing the cache.
Forks 0
Nobody has forked this yet. Be the first.
Market read
How big this is, from the evidence
- GitHub ↗Builders' pull · Medium confidence56 reactions on the issue
How these were measured: Total reactions on the GitHub issue, read from its API.
For whoever takes this up
The builder's path for this problem
Five steps, each with the tools that fit this problem and a word to carry with you. A starter prompt is ready to paste into any assistant.
Open the pathDiscussion 0
No comments yet.