-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Env creation from python 3.7 not working M1 Apple Silicon Mac (Miniconda 3) #12206
Comments
So the problem was there's no native build for python below 3.8 for Apple Silicon. As a workaround you can follow this steps to emulate x86_64 architecture in M1 Apple Silicon (ARM).
Solution from : https://stackoverflow.com/questions/70205633/cannot-install-python-3-7-on-osx-arm64 |
We said osx-arm64 not osx-x86_64, clearly this doesn't solve the problem |
Have you tried it? Works just fine on my M1 MacBook. |
@SohelKabir what are the pros and cons of emulating a different architecture on the apple silicon? |
true, "zsh: bad CPU type in executable: python" |
The same here: I am using M3 Pro chip, and this yields |
What you have to understand is that 3.7 was released before the ARM Macs were released. So nobody ever compiled 3.7 for ARM. You don't really have a choice to use emulation (Rosetta) thus forcing x86 to be able to use 3.7. And honestly why would you even bother with such an old and unsupported version anyways. 3.9.1 was the first release to natively support ARM. We're on 3.12 now for LTS! |
Totally understand your point :) I was just trying some others' code dating back to 2021, which relies on an ancient version of Tensorflow that can only run with Python 3.7 LOL Sine this is impossible I have given up this idea. |
Awesome |
Checklist
What happened?
tried to create an env with these commands both are failing on Apple Silicon Mac.
conda create -n myenv python=3.7
and with channel conda-forge.
conda create -n myenvenv -c conda-forge python=3.7
both commnad resulting same error!
Conda Info
Conda Config
Conda list
Additional Context
No response
The text was updated successfully, but these errors were encountered: