John Sirois

@phaer I just noticed all this. [Pex](https://github.com/pantsbuild/pex/) supports generating lock files for Linux and Mac and it supports cycles. It uses Pip under the covers. It also supports locking for...

As I understand it @stuhood you'll be taking up this issue at least to verify / repro the root cause since you run the OS and are in a better...

These should not be related. Prior to the _just_ released Pex 2.1.46, the venv hashes did happen to include the full python interpreter version. The scheme is: `$PEX_ROOT/venvs///`. The `pex_hash`...

Assuming the root cause guess is correct - an xcode upgraded Python that's re-directed to through a shim binary ~like this: https://github.com/python/cpython/blob/v3.7.1/Mac/Tools/pythonw.c - we've had another report in Pants Slack...

See #2342 where Pants uses the requirements file Pip option pass-through when `pex3 lock create`ing lock files and then gets bit when trying to update those lock files. The `--only-binary`...

The full reference for options that can be passed in requirements files: https://pip.pypa.io/en/stable/reference/requirements-file-format/#per-requirement-options

Hrm. Yeah, I was confused by subcommands in argparse and I think I still am. Trying to page this in, but the path you're pushing seems like the right way...

> For the second line since installing wheels into a venv is just creating hardlinks ... ~Negative. When externalizing PEX never uses symlinks or hard links back into the PEX...

Ok, for the last line `pex: Installing 22 wheels in venv at ./tenv: 3585.3ms` - that is actually the time it takes to hardlink the site-packages tree. If I switch...

Ok, so it turns out both of these cases of ~3s are all consumed in hashing distribution files. So the time taken at least makes sense now. This is hashing...