non-editable install with maturin develop --uv

[mbway]

Bug Description

if maturin develop --uv is used with an environment created with uv venv, the package is not installed in editable mode. This is likely because pip is not available in the environment and there is no fallback (but I'm not sure why fix_direct_url() isn't crashing).

Since uv 0.4.25 the tool has supported uv pip show --files so assuming maturin is OK with requiring at least this version, the fallback to always use pip in fix_direct_url() can be removed.

uv version: 0.5.5

Your maturin version (maturin --version)

maturin 1.7.6

Your Python version (python -V)

Python 3.12.2

Your pip version (pip -V)

pip 24.0

What bindings you're using

pyo3

Does cargo build work?

• Yes, it works

If on windows, have you checked that you aren't accidentally using unix path (those with the forward slash /)?

• Yes

Steps to Reproduce

The following script installs the foobar package in non-editable mode when USE_UV=1 and in editable mode when USE_UV=0 (the package is also installed in editable mode when using maturin develop --uv if the environment is created with venv):

set -e
OUT=/tmp/minimal
USE_UV=1
rm -rf $OUT

if [ $USE_UV -eq 1 ]; then
    uv venv $OUT/venv
else
    python -m venv $OUT/venv
fi

. $OUT/venv/bin/activate

maturin new --name foobar --bindings pyo3 $OUT/foobar
cd $OUT/foobar

if [ $USE_UV -eq 1 ]; then
    maturin develop --uv
else
    maturin develop
fi

uv pip list

[messense]

Pull requests are welcome!