Heyo again! I seem to have found what might be a b...
# general
g
Heyo again! I seem to have found what might be a bug?
Copy code
❯ ./pants 
./pants: line 478: /Users/user@company.com/.cache/pants/setup/bootstrap-Darwin-arm64/2.14.0_py39/bin/python: No such file or directory

❯ ls -lah /Users/user@company.com/.cache/pants/setup/bootstrap-Darwin-arm64/2.14.0_py39/bin/python
lrwxr-xr-x  1 <mailto:user@company.com|user@company.com>  staff    70B Nov 10 12:43 /Users/user@company.com/.cache/pants/setup/bootstrap-Darwin-arm64/2.14.0_py39/bin/python -> /Users/user@company.com/.pyenv/versions/3.9.13/bin/python3.9

❯ file /Users/user@company.com/.cache/pants/setup/bootstrap-Darwin-arm64/2.14.0_py39/bin/python
/Users/user@company.com/.cache/pants/setup/bootstrap-Darwin-arm64/2.14.0_py39/bin/python: broken symbolic link to /Users/user@company.com/.pyenv/versions/3.9.13/bin/python3.9
This is what I get when I try to run pants on my M1 Mac. I believe the issue might have to do with the “@” in my username since I log in using a federated account?
c
Hi! I don’t think this has to do with
@
in your username, but with the
broken symbolic link
you found there.. unless it’s broken due to the
@
but that just feels unlikely to me.
I’m on a M1 using pyenv as well, without
@
in the path, alas my
file
to the
bin/python
yields a proper executable..
Copy code
╰─❯ ll ~/.cache/pants/setup/bootstrap-Darwin-arm64/2.14.0_py39/bin/python
lrwxr-xr-x  1 andreas.stenius  staff    59B 31 Oct 09:56 /Users/andreas.stenius/.cache/pants/setup/bootstrap-Darwin-arm64/2.14.0_py39/bin/python -> /Users/andreas.stenius/.pyenv/versions/3.9.13/bin/python3.9
╰─❯ file /Users/andreas.stenius/.cache/pants/setup/bootstrap-Darwin-arm64/2.14.0_py39/bin/python
/Users/andreas.stenius/.cache/pants/setup/bootstrap-Darwin-arm64/2.14.0_py39/bin/python: Mach-O 64-bit executable arm64
╰─❯ file /Users/andreas.stenius/.pyenv/versions/3.9.13/bin/python3.9
/Users/andreas.stenius/.pyenv/versions/3.9.13/bin/python3.9: Mach-O 64-bit executable arm64
g
It turns out that just deleting the ~/.cache folder and starting over solved my problem. Odd…
👍 1
c
well I guess that recreated the symlink you had in there which was broken..