so, i'm debugging an issue that looks like it will require getting verbose logging from the

pip

invokes running under

pex

... https://github.com/pantsbuild/pants/pull/9328 propagated pants' logging to pex, but pex does not propagate its own log level to pip

I could have Sworn John did this to. Something about how Pip only goes up to

-vvv

but Pex goes up to 9

Exactly... I saw it too, heh

Ah. Probably an over sight

The Pex CLI has actually always worked this way. PEX_VERBOSE controls runtime logging of PEXes. The

-v

arg controls buildtime logging of the Pex CLI.

ENV.PEX_VERBOSE

is used as a middleman to shuffle these values around in the code. I've updated the issue and am looking at the Pants use case.

Mmm. Yes. Remembering now. The thing that threw me off is that when pex is packaged as a pex, you do get some output due to the runtime pex loading itself

@witty-crayon-22786 you're debugging v1 use of Pex via the API and not v2 use of Pex via the CLI?

I'm actually debugging direct usage of pex in the release scripts. Got the verbose output, and it looks like a tag mismatch.

OK. So, you just added -vvv... in that script.

Thanks!