Editable installs for uv tool

[blueraft]

Summary

Resolves #5436.

Test Plan

cargo test

❯ ./target/debug/uv tool install -e ~/black
warning: `uv tool install` is experimental and may change without warning
Resolved 6 packages in 894ms
   Built black @ file:///Users/ahmedilyas/black
Prepared 1 package in 468ms
Installed 6 packages in 6ms
 + black==24.4.3.dev23+g7e2afc9 (from file:///Users/ahmedilyas/black)
 + click==8.1.7
 + mypy-extensions==1.0.0
 + packaging==24.1
 + pathspec==0.12.1
 + platformdirs==4.2.2
Installed 2 executables: black, blackd

venv has the .pth files.

❯ eza /Users/ahmedilyas/Library/Application\ Support/uv/tools/black/lib/python3.12/site-packages/
_black.pth       _virtualenv.py                         click                  mypy_extensions-1.0.0.dist-info  packaging                 pathspec                   platformdirs
_virtualenv.pth  black-24.4.3.dev23+g7e2afc9.dist-info  click-8.1.7.dist-info  mypy_extensions.py               packaging-24.1.dist-info  pathspec-0.12.1.dist-info  platformdirs-4.2.2.dist-info

[charliermarsh]

Can we show the receipt here?

[charliermarsh]

Can we also add a test for uv tool install back after uv tool install -e ./scripts/packages/black_editable?

[blueraft]

Can we show the receipt here?

uv tool install exits with a failure for the black_editable package since it has no executables. So no receipt gets created in this scenario.

[charliermarsh]

Can we add an executable to it?

[blueraft]

I've added a simple executable and added additional snapshot tests.

Can we also add a test for uv tool install back after uv tool install -e ./scripts/packages/black_editable?

I added this too, but it just installs black version from the PyPi server in this case, do you think that's the right behaviour here?

[charliermarsh]

I think that's because you're creating a new context here. If you remove that, it retains the install (but the behavior is kind of confusing -- #5489 helps).

[charliermarsh]

I'd like to merge #5489 before this.

[charliermarsh]

Actually, it's ok to merge as-is. There are some confusing behaviors, but they also exist on main.