Closed jameslparks closed 2 months ago
Hey @jameslparks, thanks for reporting. Quick question, just to be sure: did you use our M1 installer for Spyder? Or the Intel one?
Closing due to lack of response.
Sorry for the delayed response. Yes I did definitely use the M1 installer for spyder
Ok, thanks for the confirmation. That's what I thought.
@mrclary, are we packing the right micromamba executable in our M1 installer for that architecture?
Ok, thanks for the confirmation. That's what I thought.
@mrclary, are we packing the right micromamba executable in our M1 installer for that architecture?
Indeed we are not sending the correct micromamba for arm64. This was an oversight when we added the arm64 builds for our 5.x standalone installer.
Thanks @mrclary for the confirmation.
@jameslparks, we'll fix this issue in our next version (5.5.6), to be released in a week or two.
@ccordoba12 is the 5.5.6 version release available yet? thanks
Yes, it is. Sorry for the delay, we were quite busy preparing Spyder 6.0 and forgot about 5.5.6. But it'll be released tomorrow.
Description
What steps will reproduce the problem?
I have installed miniconda to create new environments which i can successfully. The spyder python interpreter also recognises the environment when restarting the kernel but whenever i attempt to run some code i get the message below.
I am using a macOS M3 system and installed syper through the Spyder_arm64.dmg. Sypder all works fine when not attempting to use other environments.
/Applications/Spyder.app/Contents/Resources/lib/python3.10/spyder/plugins/ipythonconsole/scripts/conda-activate.sh: line 12: /Applications/Spyder.app/Contents/Resources/lib/python3.10/spyder/bin/micromamba: Bad CPU type in executable
Versions
Dependencies