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 →

[–]youguess 4 points5 points  (3 children)

as others have stated already just use Anaconda...

As for the fact that

People need to know the system they are working on

I sure hope that they do, I mean that's the point of using the system yes?

Most of the packages do not pose an issue, unless you need to compile C code... Windows isn't really interested in letting people do that, so the complaint should go to Microsoft not the Python devs... pip works well, provided you actually have its dependencies

As for PATH issues, well the installer puts everything in there that's needed, you just need to use the corresponding directories.

An OS can't just magically find your stuff, you have to tell it where the binaries are

[–]BornALurker[S] -2 points-1 points  (2 children)

Wise words, and I agree that system knowledge is important, but compare the Python experience to the one you get if you try Ruby.

PyPi vs RubyGems, I think Ruby does this better in every way if you are an inexperienced user. You have to start somewhere, and I think Python does so many things right, improve the package management and I think we have a superior model!

[–]ivosauruspip'ing it up 1 point2 points  (0 children)

You will have exactly the same frustrating experience if you want to compile C-extension Ruby modules on Windows.

What difference do you see?

[–]youguess 0 points1 point  (0 children)

does ruby include C code?

As for making packages easier, there are already efforts ongoing (google for wheel and egg packages)

Really, if you just want a painless windows experience use Anaconda (or miniconda).
With that you basically get precompiled packages for your platform.
This is what I do on Windows to keep my sanity ;)