I haven’t had any problems with my environment or any libraries as a consequence. I tend not to install packages with conda if I can avoid it though (despite their recommendations) and just use pip within the conda environment. I’ve somehow managed to avoid this entirely by using conda for my virtual environments. On that note, many people have reported problems getting pyenv (or virtual environments in general) to work properly on the M1, and consequently libraries installed in the environment. Just leave it be and set up whatever python you want in virtual environments. I don’t know why but it can break your entire OS. If like most pythonistas, you use 3.x, you may consider uninstalling it. MacOS comes with a python 2.7 installation. Assuming you have opened your terminal with Rosetta, you should be able to install homebrew without a hitch by following the instructions on their website.
You will likely be used to apt but with mac you ought to switch to using homebrew. zsh comes with a lot of cool features lacking in bash but if you want to stick to what you know to begin with, you can set your default shell as bash using:
More detailed instructions can be found from the team at Notion here.įinally, the default shell on mac is zsh whereas if you are coming from Ubuntu, you will be used to the standard bash. This should install itself automatically and is responsible for translating x86 code to make it compatible with Apple Silicon. However, regardless of which one you use, make sure to open with Rosetta (Rosetta 2 actually). It’s packed full of features you’d have never thought existed in a terminal. Instead of using the default macOS Terminal, I would strongly recommend using iTerm2 instead. Processor: Intel® Core™ i7-8565U CPU 1.80GHz × 8
0 kommentar(er)
