3 ms·
> Each user had 10GB of storage allocated and pip's cache was taking up a ton of space & not letting me change the location properly. Switched to uv and everyth
by yjftsjthsd-h 1y ago
> Each user had 10GB of storage allocated and pip's cache was taking up a ton of space & not letting me change the location properly. Switched to uv and everything just worked
Is it better about storage use? (And if so, how? Is it just good at sharing what can be shared?)
- fsh 1y agouv hardlinks identical packages, so adding virtual envs takes up very little space.
- snerbles 1y agoUnless you cross mount points, which uv will helpfully warn about.
- codethief 1y agoIn those situations, have you had a any luck using UV_LINK_MODE=symlink? I eventually had to resort to `copy` mode because it seemed the folder names (hashes) uv created in the package cache were not fully deterministic. So sometimes my cache volume would change and my Docker build would break. :\
- kissgyorgy 1y agoThere is a global cache for all installed packages in the user home cache dir.
- _lvbh 1y agoBoth pip and uv cache packages to ~/.cache. Uv lets you change it to /tmp and symlink instead of copying
- esseph 1y agoNote: /tmp will take awhile to get rid of, but it's definitely on the chopping block. I'd avoid workflows that lean on it, if anything else for security's sake.