-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs say cache is $HOME/Library/Caches/uv but that may not be correct #8626
Labels
Comments
I found what looks to be the real
That weird find /Users/simon/Library/Caches/com.apple.python/Users/simon/Library/Caches/uv
This one was VERY full:
du -h ~/.cache/uv | tail -n 1
|
We switched to XDG in #5806 — looks like we forgot to update this doc. It can be there for backwards compatibility reasons, but new installs use the XDG standard location. |
Also useful (for other people exploring this):
On my machine outputs:
|
simonw
added a commit
to simonw/uv
that referenced
this issue
Oct 28, 2024
charliermarsh
added a commit
that referenced
this issue
Oct 28, 2024
Refs: - #8626 ## Summary Current documentation incorrectly suggests that the macOS cache directory location is `$HOME/Library/Caches/uv`, but that changed in: - #5806 Updates docs to say this instead: > <p>Defaults to <code>$HOME/.cache/uv</code> on macOS, <code>$XDG_CACHE_HOME/uv</code> or <code>$HOME/.cache/uv</code> on Linux, and <code>%LOCALAPPDATA%\uv\cache</code> on Windows. The <code>uv cache dir</code> command will show the location of the cache directory.</p> --------- Co-authored-by: Charlie Marsh <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
The docs here:
uv/docs/reference/cli.md
Lines 90 to 92 in be92a2b
Say that the cache directory...
But... I had a look on my Mac in
~/Library/Caches
and there was nouv
folder.What I did find was this:
So either the documentation here needs updating or there's some kind of weird bug going on, or I'm missing something else.
The text was updated successfully, but these errors were encountered: