Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

imo, PATH control should always be in the hands of the user vs implicitly mutated

if I wanted to plug in my own `gunicorn` replacement in the airflwo case, it wouldnt’ be obv how to do that - or even possible, depending on the impl

well, i'm thinking PATH only in the context of main entry point's environment

whereas that flexibility would be true in the case of the pip install path

so for your wheel suggestion, just to unwind this a bit...

when i run `pip wheel --no-cache-dir --wheel-dir=./wheels airflow` ... this installs wheel and also at the same time populates ./wheels with all the airflow dependencies built as .whl files?

not sure about the ‘installs wheel’ bit - possibly

but yeah, it builds the transitive set of deps needed by `airflow` (as passed by the cli arg) as wheels and spits them into that dir

i somehow thought that said `pip install wheel --no-cache-dir --wheel-dir=...`

and then the subsequent pex `--no-pypi --find-links` tells pex to resolve only against that dir of wheels for resolution, which transitively ends up pulling in all of the prebuilt wheels

but wheel is actually an argument for pip, gotcha

kind of confusing because pip list will show 'wheel' as installed

```root@ca17dd219b30:/data# pip list
certifi (2016.2.28)
cffi (1.7.0)
cryptography (1.4)
enum34 (1.1.6)
idna (2.1)
ipaddress (1.0.16)
ndg-httpsclient (0.4.2)
pip (8.1.2)
pluggy (0.3.1)
py (1.4.31)
pyasn1 (0.1.9)
pycparser (2.14)
pyOpenSSL (16.0.0)
requests (2.10.0)
setuptools (25.1.0)
six (1.10.0)
tox (2.3.1)
urllib3 (1.16)
virtualenv (15.0.2)
wheel (0.29.0)```

however, the moment you install pip i notice that setuptools and wheel are automatically there in a `pip list` output

although i've always wondered why it doesn't show up in `pip freeze`

perhaps because to `pip install -r requirements.txt` on the other side of a `freeze` would require pre-installed pip+setuptools+wheel, which might conflict?

yeah, sounds like a reasonable explanation!

heading out for the evening - good luck w/ your investigation

thank you so much for your assistance, i really appreciate it.

Well, drat. Seems to make it through some part of the wheels collection/creation process. When I go to build the pex I get a 'Could not find compatible interpreter.'

-.txt

<@U1VDD5G0G|mhite> uploaded a file: <https://pantsbuild.slack.com/files/mhite/F1VE09M1C/-.txt|Untitled>