You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
I think this is effectively the same underlying symptom as #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:
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:
The text was updated successfully, but these errors were encountered: