This necessary given #7674? I'm just wary of adding more command-line flags without strong motivation.

They're pretty distinct i.e. I want to be able to share the output of the command in the docs but the build backend output is a lot on a trivial project. Maybe this will be solved by #3957 ?

Can you just use a ... or similar in the docs? I guess I just don't see this as very useful in practice.

Humph... easy enough to revisit if we need it later.

Want to reopen? I somewhat prefer --no-build-output so that it doesn't require users to know what a "backend" is, but understand that uv build --no-build-output may be awkward.

Want to reopen? I somewhat prefer --no-build-output so that it doesn't require users to know what a "backend" is, but understand that uv build --no-build-output may be awkward.

I felt the same thing and went back and forth. I figured it'd be better to be explicit since we don't foresee it being used by beginners? But --no-build-output sort of makes sense still... hm.