Mac M1 Monterey Installing Miniforge and Anaconda/Miniconda Side-by-Side

What people said

Recommends andrew · 2022-03 · Stack Overflow · on “Anaconda and upgrading to new M1 Mac”

2022/03/02 answers Native M1 installations are pretty simple now. Here are a few options for Miniforge and Miniconda. (1) Using Apple's instructions for Tensorflow with Miniforge This uses the same Miniforge solution mentioned above but includes an M1-optimized Tensorflow install, meaning TF has access to the M1 GPU cores. Look for the "arm64: Apple Silicon" section at: [LINK] (2) Running native M1 with Miniforge and Rosetta with Miniconda side-by-side (Jeff Heaton's tutorial from 2021/11) Jeff basically uses Apple's solution above for the native Miniforge install. [this video] (3) Using native M1 Miniconda There was a native M1 Miniconda installer published in 2021/11: Miniconda3 macOS Apple M1

Recommends Henry Death · 2022-04 · Stack Overflow · on “Install Anaconda Navigator with Miniforge (Mac with M1 chip)”

I have a MacBook with an M1 chip and have installed miniforge since this will run natively on the M1 chip. Question : How do I install Anaconda Navigator so that it uses the miniforge environment when I use it to launch Spyder and Jupyterlab? Or is this currently not possible? If I run conda install anaconda-navigator , I get a PackagesNotFoundError . I believe this is expected. If I understand correctly, one alternative is to install both miniconda (currently x86 only) and miniforge (e.g. Jeff Heaton's video [this video] ).

Cites Ankara · 2021-11 · Stack Overflow · on “miniconda installation issue on iMac with Apple M1 chip running macOS Big Sur”

In fact, it is a OS default problem. That problem means that your Mac is not seeing Rosetta at first because you haven't used an application made for Intel chips yet. To solve the problem, just initialize the .pkg , so that Mac asks you to install Rosetta (Just a one life thing). [LINK] Install Rosetta, exit installation from the .pkg and then you can bash Miniconda3-latest-MacOSX-x86_64.sh as usual. You can also continue the installation with the .pkg installer, but I don't personally like it because it puts it into the /opt/miniconda3 folder by default and it doesn't asks you about the conda init script written into the .zshrc file. This is important if you want to have both miniconda and

Cites arturomp · 2022-01 · Stack Overflow · on “How to install trax, jax, jaxlib on M1 Mac on macOS 12?”

jaxlib + jax After someone claimed success using miniforge [LINK] , I read this [LINK] and watched this [this video] to clarify using Anaconda and miniforge together. I installed miniforge with Apple's arm64 : Apple Silicon method [LINK] . For some reason when I ran miniforge's conda init it set up the initialization code in ~/.bash_profile even though I'm using the zsh shell. I tried putting the code manually instead in ~/.zprofile but it wouldn't load on interactive shells, so I just ended up putting it where Anaconda had put its initialization code, in ~/.zshrc . This made miniforge the default manager. Following the very useful video above, I created a ~/.start_anaconda.sh script so I can use

Cites JGFMK · 2024-09 · Stack Overflow · on “How can I debug Python code in the VS Code IDE when using pipx”

Right. I think Sequouia is as much to blame for this as anything. Homebrew had been installed for some stuff I do with chess apps I have installed. Somehow Python now defaulted to the brew instead of miniconda Python interpreter. I found a video from Jeff Heaton on Youtube [this video] I had followed partially and recapped part of his instructions relating to miniforge3. I found a more up to date link for miniforge3 for the ARM architecture here [LINK] I reinstalled miniforge 3 with: chmod +x Miniforge3-MacOSX-arm64-2.sh sh ~/Downloads/Miniforge3-MacOSX-arm64-2.sh Then I could use regular old pip and my environments again. Screw pipx. It's an abomination somehow baked into the brew version of Pyt