Zanie Blue

Hm, this seems challenging. We might need to copy the file into the build context? Or clone in the user's directory then move it into the cache? It's possible we'll...

Thanks! I guess we could say "For example, uv omits packages with invalid version specifiers in its metadata, which pip similarly excludes in recent versions" and punt another example to...

So you can do this with ``` UV_TOOL_BIN_DIR=/usr/local/bin uv tool install foo ``` For most purposes `uvx foo` is probably fine too. The overhead is maybe 10ms ``` ❯ time...

You can set `UV_TOOL_DIR` to change the storage directory too.

I don't think I'll be able to improve this without a minimal reproducible example so I can test improvements.

Unfortunately that ran without problems for me. If I add `UV_CACHE_DIR=/tmp/test` to the last invocation I get the failure ``` Installed 1 package in 2ms + hatchling==1.25.0 (from file:///Users/zb/workspace/uv/uvtest/hatchling-1.25.0-py3-none-any.whl) Resolved...

Or was it ``` ❯ mkdir uvtest cd uvtest uv init --lib uv venv curl -LO https://files.pythonhosted.org/packages/0c/8b/90e80904fdc24ce33f6fc6f35ebd2232fe731a8528a22008458cf197bc4d/hatchling-1.25.0-py3-none-any.whl uv pip install hatchling-1.25.0-py3-none-any.whl --no-deps UV_CACHE_DIR=/tmp/cache uv pip install . --no-deps --offline Initialized...

I don't think this is a dependency of hatchling missing, I think this is just how the cache works. So my latest invocation is: ``` mkdir uvtest cd uvtest uv...

Hm but that won't solve the `pip install` workflow here, right?

Would it also be feasible to explain _why_ we're building a package? Like are we doing it for install or just to read its metadata? Is that already obvious?