kwlzn
commented
6 years ago I think this is effectively the same underlying symptom as https://github.com/pantsbuild/pants/issues/3416, but just manifest in a more round-about way via two levels of indirect chainining w/ 2x the dangling potential (pants interpreter cache python -> pants venv linked python). but have not confirmed.
because afaik, build-support/pants_dev_deps.venv/bin/python itself is always a symlink:
$ ls -al build-support/pants_dev_deps.venv/bin/python
lrwxr-xr-x 1 kwilson staff 9 Jul 10 10:21 build-support/pants_dev_deps.venv/bin/python -> python2.7
nsaechao
I have two copies of the pants repo on my workspace under different directories, one forked and the other OSS. For reference, my forked repo is under ~/workspace/pants and OSS is under ~/workspace/nsaechao/pants.
When I tried to develop on the OSS pants, it looks like pants is attempting to use a cached python interpreter from my forked repo which does not exist. I deleted my forked pants repo due to other issues.
Reproduction Steps: 1.) git pull 2.) git clean -fdx 3.) ./pants clean-all 4.) ./pants test contrib/node/tests/::
Stack Trace: