-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why does standalone install require Python2? #371
Comments
I am not on Mac, so.. when this happens and what do you see? |
Initially I see an error about python not existing, I guessed it meant the symlink to the Python2 binary. I tried to fix this by creating the symlink pointing to the Python3 binary. Then I tried again and got the crash with icu, which #368 works around. I did manage to compile ICU 72 on my M1 Mac, but cht.sh still crashes when it tries to pull down the cheat sheets from the repository. Here is the full output minus the Test output:
Question, are there hardcoded paths in cht.sh? If yes, Thanks for looking at this. I'm here to test and provide logs for the M1/M2 Mac support. |
Wow. I can just remove comments here. Nice. :D Well, not really, but whatever. |
@hackdefendr try this route #372 - should get rid of the ICU. |
Hi hi, UPDATE
|
Python2 on Mac OS has been fully removed at the system level and cannot be installed via Homebrew anymore. I know about #327 and that #368 is waiting for approval to work around it, but Python2 is in fact uninstallable on MacOS, so unless the core dependency on Python2 is updated we will still not be able to install or even build local versions on Macs.
The text was updated successfully, but these errors were encountered: