[xenophonf]

What does uv offer over bog-standard setuptools, pip, pip-tools, and build?

Right now, the only thing I really want is dependency pinning in wheels but not pyproject.yaml, so I can pip install the source and get the latest and greatest, or I can pip install a wheel and get the frozen dependencies I used to build the wheel. Right now, if I want the second case, I have to publish the requirements.txt file and add the wheel to it, which works but is kind of awkward.

[baq]

It does everything with less surprises and faster. Just try it.

[xenophonf]

> Just try it.

I don't need to be told to RTFM. I was asking for advice. My attention span is my most valuable commodity, and since I'm not really surprised or slowed down by setuptools, etc., it sounds like uv probably isn't worth investigating.

Thanks.

[baq]

It probably is. Just try it is the advice.

[xenophonf]

That's unhelpful.

To answer my own question—and to actually help other people with similar use cases—I read about uv's build process and dependency locking. It does not appear to be able to lock dependencies for build distributions (wheels).

https://docs.astral.sh/uv/concepts/projects/build/

https://docs.astral.sh/uv/pip/compile/

However, it does mention that Python supports multiple build systems, which I didn't know, so this hasn't been a complete waste of my time.

Thanks!

[baq]

If your time is so precious that you complain about wasting it here, I don't know what to tell you, but glad you aren't going back empty handed!