John Sirois

This was obsoleted by #1133 which upgraded Pex's vendored Pip and lost support for setting custom headers at all.

The focus here has been on resolving, but I think the ~OP shows that's a detour around the block: https://github.com/pex-tool/pex/issues/1093#issuecomment-720192890 IIUC @adeandrade just wants to make a PEX from their...

Thanks @novemberkilo! It looks like a workaround then for setuptools 50 is to `export SETUPTOOLS_USE_DISTUTILS=stdlib`. That is all the 50.1.0 fix ~does. I'm pretty sure it doesn't make sense to...

This problem no-longer reproduces with modern Pex: ``` :; python3.5 -mvenv .venv :; .venv/bin/pip --cert /etc/ssl/certs/ca-certificates.crt install pex~=2.1 setuptools==50 Collecting pex~=2.1 Using cached https://files.pythonhosted.org/packages/de/45/94497d22a1517b2462394f641ea272e7ec624823f223c01a5f0d7e6f571d/pex-2.16.2-py2.py3-none-any.whl Collecting setuptools==50 Cache entry deserialization failed,...

`PEX_VERBOSE` has never propagated to the Pex CLI beyond its own bootstrap if the CLI itself is PEXed. In short the `PEX_VERBOSE` environment variable controls PEX file runtime logging. The...

This was fixed in 2.1.51 although I can't identify the commit that fixed it: ```console # Broken: :; curl -sfL https://github.com/pex-tool/pex/releases/download/v2.1.50/pex > ~/Downloads/pex && chmod +x ~/Downloads/pex :; PEX_VERBOSE=3 python3.8...

With the introduction of `InterpreterTest` in #1770, which confirms an interpreter can resolve the PEX before committing to it, this issue should be resolved. I usually like to test these...

This has been fixed by the passage of time and the resolution of the Pip issue you pointed to. Pex currently uses hatch as its build system, but that doesn't...

This appears to be related to #340. I've picked that up and will close this if it fixes. I think it does.

This is now fixed. My test rig: ```console # Simple project using versioneer 0.16.0 which was latest at the time of the OP. # /tmp/issues/235 :; tree . ├── setup.cfg...