-vv is not passed to build env install subprocesses #12577
Labels
Comments
markmc
added
S: needs triage
markmc
added a commit
to markmc/pip
that referenced
this issue
Mar 14, 2024
Fixes pypa#12577 This looks like it was an oversight in pypa#9450 - we should pass the correct verbosity level to build env install subprocesses. Tested with: ``` rm -rf ~/.cache/pip && rm -f *.whl && pip wheel --no-binary :all: hatchling ``` and all three verbosity levels, before and after this change, giving the following logs: ``` 33 patched-verbosity0.log 2549 patched-verbosity1.log 11938 patched-verbosity2.log 33 unpatched-verbosity0.log 99 unpatched-verbosity1.log 1030 unpatched-verbosity2.log ``` i.e. currently a lot of useful logs are being dropped from these install subprocesess even with -vvv
markmc
added a commit
to markmc/pip
that referenced
this issue
Mar 15, 2024
Fixes pypa#12577 This looks like it was an oversight in pypa#9450 - we should pass the correct verbosity level to build env install subprocesses. Tested with: ``` rm -rf ~/.cache/pip && rm -f *.whl && pip wheel --no-binary :all: hatchling ``` and all three verbosity levels, before and after this change, giving the following logs: ``` 33 patched-verbosity0.log 2549 patched-verbosity1.log 11938 patched-verbosity2.log 33 unpatched-verbosity0.log 99 unpatched-verbosity1.log 1030 unpatched-verbosity2.log ``` i.e. currently a lot of useful logs are being dropped from these install subprocesess even with -vvv
markmc
added a commit
to markmc/pip
that referenced
this issue
Mar 20, 2024
Fixes pypa#12577 This looks like it was an oversight in pypa#9450 - we should pass the correct verbosity level to build env install subprocesses. Tested with: ``` rm -rf ~/.cache/pip && rm -f *.whl && pip wheel --no-binary :all: hatchling ``` and all three verbosity levels, before and after this change, giving the following logs: ``` 33 patched-verbosity0.log 2549 patched-verbosity1.log 11938 patched-verbosity2.log 33 unpatched-verbosity0.log 99 unpatched-verbosity1.log 1030 unpatched-verbosity2.log ``` i.e. currently a lot of useful logs are being dropped from these install subprocesess even with -vvv
arenasys
pushed a commit
to arenasys/pip
that referenced
this issue
Mar 26, 2024
Fixes pypa#12577 This looks like it was an oversight in pypa#9450 - we should pass the correct verbosity level to build env install subprocesses. Tested with: ``` rm -rf ~/.cache/pip && rm -f *.whl && pip wheel --no-binary :all: hatchling ``` and all three verbosity levels, before and after this change, giving the following logs: ``` 33 patched-verbosity0.log 2549 patched-verbosity1.log 11938 patched-verbosity2.log 33 unpatched-verbosity0.log 99 unpatched-verbosity1.log 1030 unpatched-verbosity2.log ``` i.e. currently a lot of useful logs are being dropped from these install subprocesess even with -vvv
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
While using
-vvI noticed seeing a big pause between these two output lines:Installing backend dependencies: started Installing backend dependencies: finished with status 'done'Clearly a lot of stuff was happening - like wheel building - but there was no output
It turns out that when -vv was introduced in #9450 this higher verbosity level was not passed onto these subprocesses
Expected behavior
No response
pip version
24.0
Python version
3.9
OS
RHEL
How to Reproduce
Compare the logging output from
before and after the patch. I'm seeing 1k lines before and 12k lines after.
Output
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: