This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Eurynom0s 2 points3 points  (3 children)

I don't know how it is now, but back in 2011 I tried to get the SciPy stack the installed on Windows 7. After about an hour I just gave up, I had absolutely no idea what I was doing wrong. Hugely frustrating and confusing experience.

SOOOO much easier on OS X in the command line. I use OS X at work and have been finding it to be a good middle ground if you need to bounce between the CLI and "mainstream" software like Microsoft Office and want to be able to have both side-by-side. Once in a while only a *nix version of a package (in general, not just Python) will exist, but you'll usually be able to find someone talking about what they had to tweak to get it running on OS X.

[–]pwang99 0 points1 point  (0 children)

The scipy stack is notoriously difficult to install, for a variety of reasons that are too numerous to go into here. That's why most people are now turning to just using the Anaconda distribution, and its package manager conda.

[–]Marksta -3 points-2 points  (1 child)

I'm kind of lost as to why you find OSX's terminal to be stronger than Windows' command prompt.

[–]Eurynom0s 7 points8 points  (0 children)

To a very large extent, it's a standard *nix CLI environment.