Option to disable capture of stdout coming from setup.py

[paugier]

When 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.

[uranusjr]

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.

[pradyunsg]

Consider using --log, which lets you dump the verbose output into a file for inspection.

[paugier]

Consider using --log, which lets you dump the verbose output into a file for inspection.

I think that for developers of a project it would be much better to get the output of the setup.py of the project directly.

These types of output come from setuptools or pip ?

1 location(s) to search for versions of sphinx:
* https://pypi.org/simple/sphinx/
Getting page https://pypi.org/simple/sphinx/
Found index url https://pypi.org/simple
Looking up "https://pypi.org/simple/sphinx/" in the cache
Request header has "max_age" as 0, cache bypassed
https://pypi.org:443 "GET /simple/sphinx/ HTTP/1.1" 200 30989
Updating cache with response from "https://pypi.org/simple/sphinx/"
Caching due to etag
Using version 3.2.1 (newest of versions: 0.1.61611, 0.1.61798, 0.1.61843, 0.1.61945, 0.1.61950, 0.2, 0.3, 0.4, 0.4.1, 0.4.2, 0.4.3, 0.5, 0.5.1, 0.5.2, 0.6, 0.6.1, 0.6.2, 0.6.3, 0.6.4, 0.6.5, 0.6.6, 0.6.7, 1.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.1, 1.1.1, 1.1.2, 1.1.3, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.3, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.6, 1.4, 1.4.1, 1.4.2, 1.4.3, 1.4.4, 1.4.5, 1.4.6, 1.4.7, 1.4.8, 1.4.9, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.5.4, 1.5.5, 1.5.6, 1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5, 1.6.6, 1.6.7, 1.7.0, 1.7.1, 1.7.2, 1.7.3, 1.7.4, 1.7.5, 1.7.6, 1.7.7, 1.7.8, 1.7.9, 1.8.0, 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.8.5, 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 3.0.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, 3.1.0, 3.1.1, 3.1.2, 3.2.0, 3.2.1)
Collecting sphinx
  Created temporary directory: /tmp/pip-unpack-zh7zte2m
  Looking up "https://files.pythonhosted.org/packages/63/b8/34ba32a94cb2b223b941e43b3bcab11281763b95daa8587879eec1eb9a62/Sphinx-3.2.1-py3-none-any.whl" in the cache
  No cache entry available
  https://files.pythonhosted.org:443 "GET /packages/63/b8/34ba32a94cb2b223b941e43b3bcab11281763b95daa8587879eec1eb9a62/Sphinx-3.2.1-py3-none-any.whl HTTP/1.1" 200 2868133
  Downloading Sphinx-3.2.1-py3-none-any.whl (2.9 MB)
  Ignoring unknown cache-control directive: immutable
  Updating cache with response from "https://files.pythonhosted.org/packages/63/b8/34ba32a94cb2b223b941e43b3bcab11281763b95daa8587879eec1eb9a62/Sphinx-3.2.1-py3-none-any.whl"
  Caching due to etag
  Added sphinx from https://files.pythonhosted.org/packages/63/b8/34ba32a94cb2b223b941e43b3bcab11281763b95daa8587879eec1eb9a62/Sphinx-3.2.1-py3-none-any.whl#sha256=ce6fd7ff5b215af39e2fcd44d4a321f6694b4530b6f2b2109b64d120773faea0 (from fluidfft==0.3.1) to build tracker '/tmp/pip-req-tracker-fl9nz_fx'
  Removed sphinx from https://files.pythonhosted.org/packages/63/b8/34ba32a94cb2b223b941e43b3bcab11281763b95daa8587879eec1eb9a62/Sphinx-3.2.1-py3-none-any.whl#sha256=ce6fd7ff5b215af39e2fcd44d4a321f6694b4530b6f2b2109b64d120773faea0 (from fluidfft==0.3.1) from build tracker '/tmp/pip-req-tracker-fl9nz_fx'

[uranusjr]

I believe these all come from pip.

[paugier]

Then it would really be convenient to be able to get the output coming from the setup.py of the project but without these lines (they can be multiplied by a large number of packages).

pip install -e . hides everything and pip install -v -e . is too verbose.

Maybe such lines could be displayed only with pip install -vv -e . ? Or one can use a new flag, something like no-stdout-capture ?

[minrk]

I've wanted this for so long! I think it would be awesome and more intuitive (for me, at least) for -v to 'hide less' and -vv to be required to show the more detailed debug output. I looked into it a little bit and it seems a bit tricky because only log levels are used currently to distinguish between all levels of verbosity and default output, and there isn't a level between DEBUG and INFO. In fact, I can't find any situation where -vv behaves any differently from -v, as verbosity only appears to be used here, where all values >= 1 are treated the same. -vv only appears to be distinguished from -v if -q is also specified somewhere, affecting the sum here.

[paugier]

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.