-v shows subprocess output #9447
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
verbosity level 1 sets subprocess log level to debug (showing subprocess output), while level 2 sets all logging to debug-level. This solves the common problem of disabling suppression of setup.py output without being buried in debug output of getting dependencies from PyPI. Closes #8856.
requires
-vvto enable full debug-level output, which is the current behavior of-v.It would map more naturally to the multi-level
-vvvto have more than one two log levels, as-vvcurrently produces exactly the same output as-v, as far as I can tell. But I expect that using custom log levels (e.g. 15 for VERBOSE) is probably not preferred? The python docs argue pretty strongly against custom log levels, but they are supported, if that seems better.TODO: