Timeline for What is the currently recommended way to install the SciPy ecosystem on OS X?
Current License: CC BY-SA 3.0
9 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 8, 2016 at 18:17 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
May 9, 2016 at 17:30 | answer | added | user7257 | timeline score: 0 | |
May 8, 2016 at 16:25 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
Apr 8, 2016 at 15:42 | answer | added | Feffe | timeline score: 1 | |
Mar 12, 2016 at 21:08 | comment | added | Eliad | I don't think this is the place for this question. You should have asked it on SO, Unix SE or Super User. | |
Mar 11, 2016 at 13:01 | history | tweeted | twitter.com/StackSciComp/status/708276786220703744 | ||
Mar 9, 2016 at 10:58 | answer | added | origimbo | timeline score: 0 | |
Mar 9, 2016 at 10:32 | comment | added | Christian Clason | I use homebrew for the same reasons you mention, and haven't had any real trouble (excepting a premature switch to El Capitan). In particular, you can control via options whether you want to build from a stable release or the current developer repository, and, specifically for NumPy/SciPy, to build and link against OpenBLAS. Upgrading is also easy. As a rule of thumb, everything that can be installed via homebrew, I do so -- particularly packages that need to build and link against external libraries -- and resort to pip only for pure Python packages not distributed via homebrew (e.g., Sympy). | |
Mar 9, 2016 at 10:11 | history | asked | N. Virgo | CC BY-SA 3.0 |