maturin failed, Caused by: failed to list package files

[ClementWalter]

I'm just starting with maturin and doing the init code

maturin init -b pyo3 --mixed
maturin develop --uv

fails with

🍹 Building a mixed python/rust project
🔗 Found pyo3 bindings
🐍 Found CPython 3.10 at /Users/clementwalter/Documents/string_sum/.venv/bin/python
📡 Using build options features from pyproject.toml
Audited 2 packages in 0.48ms
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.01s
📦 Built wheel for CPython 3.10 to /var/folders/7y/kppn0q7946gczmpmnlc5bncm0000gn/T/.tmphpDGPx/string_sum-0.1.0-cp310-cp310-macosx_11_0_arm64.whl
✏️  Setting installed package as editable
💥 maturin failed
  Caused by: failed to list package files

I've tried to add more logs with -vvv but it doesn't display any information on the error.

The code is https://github.com/ClementWalter/string_sum

[ClementWalter]

I have tried to investigate a bit more and I'm wondering if it's not related to how uv manages pip. See also astral-sh/uv#6593.

Adding uv add pip, maturin develop --uv still fails but maturin develop works (!).

Note that in any cases (even when it fails), maturin build does work, and the packaging is ready, since the test passes

[messense]

What's your uv version? I think maturin develop --uv currently requires uv 0.4.25 and later.

The error comes from here

maturin/src/develop.rs

Line 273 in 5342a83

ensure!(output.status.success(), "failed to list package files");

cc @mbway

[mbway]

Yeah, old UV doesn't support pip show --files

Should I put a check in place that gives a more informative error if a UV is used that is too old?

[messense]

That'd be great, but IMO a simpler solution is just change the error message to say that we require uv >= 0.4.25.

[ClementWalter]

was actually using uv 0.4.9 (77d278f68 2024-09-10

[mbway]

the way versions are ordered, 0.4.9 is older than 0.4.25. I have a PR that improves the error message #2389