I'm getting a pip install error when building one of my PEXes. I've set

PEX_VERBOSE=9

in the

__run.sh

, but the error is still not plain to me.

pip._internal.exceptions.InstallationSubprocessError: Getting requirements to build wheel exited with 1
There was 1 error downloading required artifacts:secrets<0.9.0,>=0.8.11) :: Resolving requirements from lock file tickets-poetry.lock :: Categorizing 51 downloaded artifacts
1. pyyaml 5.4.1 from https://<internal_company_url>/api/pypi/pypi-virtual/packages/packages/a0/a4/<sha>/PyYAML-5.4.1.tar.gz

Does anyone know how I can preserve even more logs to troubleshoot this? I'm assuming the issue is related to the version of pyyaml (which unfortunately I can't upgrade). I found in a different thread that someone suggested

--preserve-pip-download-log

on the

pex

command inside

__run.sh

, but this isn't producing any additional output, as far as I can tell.

I think

--preserve-pip-download-log

will mean `pex`'s logging includes a file path that contains the pip log, rather than including it directly in

pex

's logging.

What @broad-processor-92400 says is true, but looking at the text you provided @acoustic-library-86413 is "secrets" an internal project that collides with this?: https://pypi.org/project/secrets/#history or did your org make its own version of that and upload it to your company index?

secrets

is a modified name in the example I gave, so there shouldn't be any collision issues. I'll try to look for the log file with decreased verbosity level. Thanks for the input everyone. I did try to grep for "log" in the output without any luck initially.

Looks like so:

$ pex.venv/bin/pex3 lock create cowsay --preserve-pip-download-log > lock.json
pex: Preserving `pip download` log at /tmp/pex-pip-log.6citami6/pip.log
...

Based on your previous question about interpreter constraints, I suspect this is related. I recommend constraining to a single interpreter each time (e.g.,

==3.9.2

) and not a range, and certainly not an open-ended range like

>=3.9.2

.

Fair point, Benjy

You don't want pex to attempt to resolve for multiple interpreter versions, when you only care about one.