FR: Support installing and managing uv with uv tool

[weihenglim]

Currently the documentation's recommended way of installing uv is via pipx. With the release of uv tool, it would be great to let uv manage itself, similar to how you can do pipx install pipx.

When testing on my Windows 11 machine, uv tool install uv works but the tool breaks when attempting to upgrade uv to the latest version:

> uv tool upgrade uv 
Resolved 1 package in 38ms
Prepared 1 package in 1ms
Installed 1 package in 8ms
 + uv==0.3.1
error: failed to remove file `C:\Users\User\.local\bin\uv.exe`
  Caused by: Access is denied. (os error 5)

> uv tool list
warning: Ignoring malformed tool `uv` (run `uv tool uninstall uv` to remove)

[charliermarsh]

Ahh yeah, that's a known issue on Windows: #1368. You should be able to do uv self update if you installed via the standalone installers (as opposed to through pip or similar).

[weihenglim]

Ah that's a shame, was hoping it would be possible to just upgrade everything (including uv itself) with a single uv tool upgrade --all command. Guess I'll stick with the standalone installers for now.

[zanieb]

I'm not sure it makes sense to manage uv with uv, it creates a weird chicken and egg problem. You can definitely do uvx uv@version though!

[konstin]

rustup update updates both its managed toolchains, then does a self update, we should consider a similar convenience function for uv.

[zanieb]

Hm like uv upgrade?

• Upgrade self
• Upgrade all tools
• Upgrade all Python versions

Could be cool.