Display the built file name instead of the canonicalized name in uv build

[dimbleby]

Summary

eg

curl -O https://files.pythonhosted.org/packages/ea/46/f44d8be06b85bc7c4d8c95d658be2b68f27711f279bf9dd0612a5e4794f5/ruamel.yaml-0.18.10.tar.gz
uv build --wheel ruamel.yaml-0.18.10.tar.gz

giving output that ends Successfully built ruamel_yaml-0.18.10-py3-none-any.whl

but this is not true, the setuptools backend is not PEP491 compliant, so the file that is actually built is ruamel.yaml-0.18.10-py3-none-any.whl.

I guess uv is assuming that the output is always spec-compliant?

It's a pretty minor confusion.

(Also this particular example should go away soon, there's a pull request open in setuptools for PEP491-compliance that looks likely to merge any day now.)

Platform

ubuntu 24.04

Version

0.5.25

Python version

3.13

[konstin]

Your guesses are right: uv is parsing the filename and using its normalized string printer for it. This would always be the same value for a spec-compliant build backend, which setuptools isn't (pypa/setuptools#4766). We could warn about this but it's not something the user can fix (#8203).

[zanieb]

Why not display the unparsed file name? i.e., what does parsing / normalizing get us?

[charliermarsh]

I don't think we even have it. We probably store the WheelFilename.

[charliermarsh]

Oh nevermind, we do get it back from the build backend. We should just show the "real" filename.

[konstin]

The parsing part gives us a correctness check that the output file is valid and not an error. We can change the message to verbatim independent of that.