Build Verbosity 3 not supported anymore?

[Laky-64]

Description

Now when I try to build with verbosity set up to 3, I receive these errors

cibuildwheel: build_verbosity 3 is not supported for build frontend. Ignoring.

Build log

https://github.com/pytgcalls/ntgcalls/actions/runs/14098238434

CI config

https://github.com/pytgcalls/ntgcalls/actions/runs/14098238434/workflow#L155-L169

[henryiii]

The build frontend is now the default (not in a release yet, will be part of 3.0). The pip backend had multiple verbosity settings, but build does not, it does not hide the build output like pip does. (Build backends have never been able to take advantage of verbosity levels, so higher levels just mean pip spits out more resolving info).

[joerick]

Honestly, it might be worth deprecating this feature. As you say, henryiii, it doesn't generalise well, and the flag on pip can now be set with build-frontend: pip; args: -vvv

[henryiii]

Build (also uv) does support one level of verbosity. It's just the more-than-one value that's not supported by the other backends.

[henryiii]

Interesting, we don't support level 1 for build, build[uv], or the upcoming uv. I think the reason for that is those don't hide output, so verbose=1 is useful to get build output for pip, but that's default for the others. Maybe we could map verbose > 1 to -v for those backends? -v is very similar to -vv for pip for both backends.

[Laky-64]

So I didn't understand, is a bug or something on purpose? Since without setting anymore the verbosity, it doesn't raises the warnings anymore, but at same time I'm able to see build logs

[henryiii]

It's poorly worded. build (which is the default build frontend in cibuildwheel 3) does not hide the build logs like pip does. So any verbosity setting doesn't really affect build.

In #2339, I've expanded the build backend to allow verbosity 2+ to pass -v, which for build will add the extra resolver info that -vv and higher do for pip.

Just curious, why are you setting verbosity 3 instead of 1? Higher levels of verbosity do not affect the build backend (there's no way to communicate verbosity to the build backend from the build frontend), it just adds resolver info about downloading dependencies before the build.

[Laky-64]

It's poorly worded. build (which is the default build frontend in cibuildwheel 3) does not hide the build logs like pip does. So any verbosity setting doesn't really affect build.

In #2339, I've expanded the build backend to allow verbosity 2+ to pass -v, which for build will add the extra resolver info that -vv and higher do for pip.

Just curious, why are you setting verbosity 3 instead of 1? Higher levels of verbosity do not affect the build backend (there's no way to communicate verbosity to the build backend from the build frontend), it just adds resolver info about downloading dependencies before the build.

Because previously on python3.10 and upper (I'm talking some years ago), was a mandatory to use -vvv, since my project is built with cmake, and I've always used pip, so I used always in that way, But as you said, I noticed that by removing the verbosity here, the build logs actually still pop up.