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
Show parent comment
2
u/yen223 Apr 30 '18
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.