Conversation
| uv follows platform conventions for determining where to store different types of data. | ||
|
|
||
| Generally, it's best to configure these rather than each uv-specific storage location. |
There was a problem hiding this comment.
We should mention that we XDG on Unix specifically here, otherwise it's unclear what platform conventions we mean.
There was a problem hiding this comment.
I do think this becomes clear in the next section, but I think I can add something.
|
|
||
| For temporary files and caches: | ||
|
|
||
| - `$XDG_CACHE_HOME/uv` or `$HOME/.cache/uv` on Unix systems |
There was a problem hiding this comment.
We should be using either $HOME or ~ throughout the document.
|
|
||
| - `$XDG_BIN_HOME`, `$XDG_DATA_HOME/../bin`, or `~/.local/bin` on all platforms | ||
|
|
||
| ## Cache |
There was a problem hiding this comment.
This section is duplicated with the "Cache directory" in cache.md
| uv uses a local cache to avoid re-downloading and re-building dependencies. The cache contains | ||
| wheels, source distributions, responses from package indexes, Git repositories, and Python | ||
| interpreter metadata. |
There was a problem hiding this comment.
Can we add a note that the cache needs to be on the same filesystem as the venv for best performance?
There was a problem hiding this comment.
That seems like a cache.md thing, but yes.
There was a problem hiding this comment.
When reviewing I've struggled with which information goes here vs. in one of the detailed (concept) pages.
There was a problem hiding this comment.
Yeah I think this page is a bit weird and will be duplicative in some ways. I can spend more time on it though, I put this up very quickly.
| uv can install Python applications as tools using `uv tool install`. Each tool gets its own isolated | ||
| environment. | ||
|
|
||
| By default, tools are installed in the [data home](#data) under a `tools/` subdirectory, e.g., |
There was a problem hiding this comment.
In "Tools directory" in tools.md, we call this directory "application state directory" instead.
There was a problem hiding this comment.
Thanks! I didn't look at cache.md or tools.md at all yet, so I'll see what I can do to make the relationship clearer between these documents and use consistent language.
|
|
||
| uv follows platform conventions for determining where to store different types of data. | ||
|
|
||
| Generally, it's best to configure these rather than each uv-specific storage location. |
There was a problem hiding this comment.
It may be worth crosslinking or updating to the XDG section in reference/environment.md to this document
- https://docs.astral.sh/uv/reference/environment/#xdg_bin_home
- https://docs.astral.sh/uv/reference/environment/#xdg_cache_home
- https://docs.astral.sh/uv/reference/environment/#xdg_config_dirs
- https://docs.astral.sh/uv/reference/environment/#xdg_config_home
- https://docs.astral.sh/uv/reference/environment/#xdg_data_home
There was a problem hiding this comment.
I don't think we have the infrastructure to properly cross-link from the environment variable reference yet.
3 participants
We're getting questions about this. It seems best to consolidate this information?