Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I would appreciate a less verbose build option #772

Open
BMaxV opened this issue Apr 19, 2024 · 4 comments
Open

I would appreciate a less verbose build option #772

BMaxV opened this issue Apr 19, 2024 · 4 comments

Comments

@BMaxV
Copy link

BMaxV commented Apr 19, 2024

Hello everyone,

The default

python -m build

lists a lot of interactions with files that I don't want to see (600 lines). I really only want to know if the build succeeded or not.

can I have a

python -m build --quiet

or something that just tells me Successfully built foobar.whl? I can just pipe it to a file but that doesn't tell me success y/n.

Thank you for your work and this software!

@abravalheri
Copy link
Collaborator

abravalheri commented Apr 19, 2024

If you are using setuptools as backend, you can try:

python -m build -C--quiet

To reduce de verbosity (it will not reduce to 1 line though).

@henryiii
Copy link
Contributor

Build does not interfere with the build backend's output. That's why build backends like scikit-build-core produce colorful output with build, and not with pip (which captures and reprints the output). Build backends generally have verbosity toggles. Setuptools is the only one that is extremely verbose by default.

That said, it might not be a bad idea, I'm +0.1 on it. You can do && echo "Success" || echo "Failed", I think.

@henryiii
Copy link
Contributor

I'd like some way to communicate to tools what the built distributions were, but that's tricky to do since stdout/stderr are being written to by the build backend. uv does this by writing to a file, that might be what we have to do. Might be related.

@layday
Copy link
Member

layday commented Apr 20, 2024

I'd like some way to communicate to tools what the built distributions were, but that's tricky to do since stdout/stderr are being written to by the build backend. uv does this by writing to a file, that might be what we have to do. Might be related.

This is #198 - let's discuss it there.

@BMaxV BMaxV closed this as completed Apr 20, 2024
@BMaxV BMaxV reopened this Apr 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants