We only use Anaconda for the convenience of installation of Python and the main packages, not the other stuff that comes with it as well. Homebrew (Mac only) If you want a bit more control over your Python distribution, then using Homebrew to install Python is useful. It also installs the package manager pip for you, which is very useful. Gdbm: 1.19: GNU database manager: mpdecimal: 2.5.1: Library for decimal floating point arithmetic: openssl@1.1: 1.1.1k: Cryptography and SSL/TLS Toolkit: readline. A brew upgrade upgraded my system Python to Python 3.7. Unfortunately, Python 3.7 breaks other software I need to use (including but not limited to Ansible). I imagine these problems will be worked. A Computer programming portal. Discussing All programming language Solution. It contains well explained article on programming, technology.
Instructions for a supported install of Homebrew are on the homepage.
This script installs Homebrew to its preferred prefix (/usr/localfor macOS Intel, /opt/homebrew for Apple Silicon) so thatyou don’t need sudo when youbrew install. It is a careful script; it can be run even if you have stuffinstalled in /usr/local already. It tells you exactly what it will do beforeit does it too. You have to confirm everything it will do before it starts.
macOS Requirements
- A 64-bit Intel CPU or Apple Silicon CPU 1
- macOS Mojave (10.14) (or higher) 2
- Command Line Tools (CLT) for Xcode:
xcode-select --install,developer.apple.com/downloads orXcode3 - A Bourne-compatible shell for installation (e.g.
bashorzsh) 4
Git Remote Mirroring
You can set HOMEBREW_BREW_GIT_REMOTE and/or HOMEBREW_CORE_GIT_REMOTE in your shell environment to use geolocalized Git mirrors to speed up Homebrew’s installation with this script and, after installation, brew update.
The default Git remote will be used if the corresponding environment variable is unset.
Alternative Installs
Linux or Windows 10 Subsystem for Linux
Check out the Homebrew on Linux installation documentation.
Untar anywhere
Just extract (or git clone) Homebrew wherever you want. Just avoid:
Osx Homebrew Anaconda
- Directories with names that contain spaces. Homebrew itself can handle spaces, but many build scripts cannot.
/tmpsubdirectories because Homebrew gets upset./swand/opt/localbecause build scripts get confused when Homebrew is there instead of Fink or MacPorts, respectively.
However do yourself a favour and install to /usr/local on macOS Intel, /opt/homebrew on macOS ARM,and /home/linuxbrew/.linuxbrew on Linux. Some things maynot build when installed elsewhere. One of the reasons Homebrew justworks relative to the competition is because we recommend installinghere. Pick another prefix at your peril!
Multiple installations
Create a Homebrew installation wherever you extract the tarball. Whichever brew command is called is where the packages will be installed. You can use this as you see fit, e.g. a system set of libs in /usr/local and tweaked formulae for development in ~/homebrew.
Uninstallation
Uninstallation is documented in the FAQ.
1 For 32-bit or PPC support seeTigerbrew.
Conda Install Python2
2 10.14 or higher is recommended. 10.9–10.13 aresupported on a best-effort basis. For 10.4-10.6 seeTigerbrew.
3 Most formulae require a compiler. A handfulrequire a full Xcode installation. You can install Xcode, the CLT, or both;Homebrew supports all three configurations. Downloading Xcode may require anApple Developer account on older versions of Mac OS X. Sign up for freehere.
4 The one-liner installation method found onbrew.sh requires a Bourne-compatible shell (e.g. bash orzsh). Notably, fish, tcsh and csh will not work.
byIfu AniemekaonAugust 29, 2017
Fixing conflicts between Anaconda and Homebrew
Homebrew Anaconda 3
I recently installed Anaconda to my local machine and noticed that Anaconda modified my PATH variable. For Mac installations, if you check your .bash_profile, you should see something like the following:
Now if you run brew doctor, you'll get the following gnarly message:
Basically, the universe will collapse upon itself because you thought it might be cool to try a Kaggle competition.
Damn.
Fortunately, the message includes a fix - remove Anaconda from $PATH, run brew, then add Anaconda back to $PATH. Having said that, doing that every time I use Homebrew sounds like a pain in the backside.
So here's a bash script to do it for you so you can keep on being lazy.
There are aliases for the addition and removal of Anaconda from $PATH to make doing it manually even easier.
Happy (data science) coding!
Photo by Samuel Zeller on Unsplash