Option to disable capture of stdout coming from setup.py
See original GitHub issueWhen using pip for local install of a developed package with something like pip install -e .
, it is sometime useful to see what is printed in setup.py.
The capture of stdout can be disabled with the verbose option but then pip is much too verbose.
It would be useful to have a way to only disable the capture of stdout coming from setup.py but without too much verbosity of pip.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Disable output buffering - python - Stack Overflow
One way to get unbuffered output would be to use sys.stderr instead of sys.stdout ...
Read more >How to capture stdout/stderr output — pytest documentation
Setting capturing methods or disabling capturing¶ ; sys level capturing: Only writes to Python files ; sys.stdout and ; sys.stderr will be captured....
Read more >Logging - Django documentation
Setting LOGGING_CONFIG to None only means that the automatic configuration process is disabled, not logging itself. If you disable the configuration process, ...
Read more >How to redirect shell command output | Enable Sysadmin
Types of output. Commands and scripts in a shell can generate two basic types of outputs: STDOUT: The normal output from a command/script...
Read more >How to Collect, Customize, and Centralize Python Logs
configure multiple loggers and automatically capture the logger name; use fileConfig() to implement custom formatting and routing options ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
IMO pip should respect the build backend’s opinion on what is considered relevant, and not step over and decide things for it. If you feel setuptools’s output is too noisy, you should lobby for setuptools to reduce the default verbosity instead.
It would be really nice to consider this issue and PR #9450 which would fix it.
The current behavior (
-v
triggering the output of hundreds of lines about the internal of pip / setuptools) is really annoying.