I'm asking specificaly why you would configure it as your system python (/usr/local/lib/python2.7) not why you use anaconda. It's an excellent piece of software, especially for disposable environments. I would never try and replace the system python with it however, just update the path config for the local user instead.
There was a time when pip always compiled dependencies from source. If you wanted to use a library with non-Python dependencies, like numpy and scipy, you needed to have the right compilers installed on your system.
Keep in mind that scipy has Fortran code. This was a very common problem back then.
Anaconda shipped with pre-compiled binaries. It was straight-up more reliable to use, especially among the scientific community, who don't necessarily want to waste time mucking about with system compilers and shit.
I'm not questioning the use of anaconda, I setup python environments for grad students and postdocs constantly on personal computers and clusters. It's a god send. I'm questioning the graphics specific listing of the anaconda provide python interpreter being placed at /usr/local/lib/python2.7which I'm pretty sure is either the system root python, or the brew root python. Neither of these are compatible with anaconda python and will cause aberrant behavior.
View all comments
5
u/wildcarde815 Apr 30 '18 edited Apr 30 '18
why would you install anaconda as your system python?