John Sirois

A read-only env variable, say PEX_VERSION, seems reasonable to me - but it is not robust. If running from a pex you then subproccess execute some other python code, that...

@fhoering I think this is now possible is two ways: 1. PEXes now export `PEX` pointing to the originating PEX file, packed PEX directory or loose PEX directory that launched...

@fhoering I'm going to assume this works for you or would have and close this issue. Both the env var approach and the ~API approach work. A small Pex library...

> I guess I don't feel too strongly about this, but I think it would be good to be fairly confident that "every target is named" is the direction we...

> What was the reason for their excitement in 2015? That's before my time. I'm not exactly sure. I _liked_ maintaining build files and dependencies - it gave an opportunity...

Pants will support this as soon as #3063 is fixed. In short, at that point Pants will support specifying any requirement string Pip supports and Pip does support specifying local...

> Pants will support this as soon as #3063 is fixed. This assertion was false. To support a vendored wheel checked in to a repo Pants needs to support both...

To make the above a bit more concrete, using the example-python repo, you can vendor a wheel like so: ```diff $ git diff --cached diff --git a/requirements.txt b/requirements.txt index ffab1be..ea93824...

It's supported by Pex with `--path-mapping` but Pants does nothing with this feature yet.

They did, but we still can't support `ansicolors @ file://$PWD/vendored/ansicolors-1.1.8-py2.py3-none-any.whl` in the originating requirements file IIUC. We have toml support for doing something like this but neither BUILD support, nor...