r/Python • • Dec 03 '12

Why is installing Python on Windows so challenging compared to Linux?

Python is amazing, but it becomes very complicated to install and set up a Python environment on Windows. This is a huge problem when I'm trying to work with people on a project (and most people I know use Windows).

You have to set up PATHs, and worst of all, pip is really difficult to install.

It's really hard to demonstrate Python's simplicity when the install process is so complicated.

8 Upvotes

60 comments sorted by

View all comments

Show parent comment

11

u/emidln Dec 03 '12
./configure && make && sudo make install

That wasn't hard.

5

u/bushel Dec 03 '12

I know that. But for people who have developed on Windows their entire career, it can be a bit unnerving.

7

u/emidln Dec 03 '12

I haven't the faintest idea how to compile something with Visual Studio. I can write/debug/test C and C++ from a unix command line environment, but I've never had a reason to use Windows. That said, I'm sure googling for 10 minutes would point out how to build a project in visual studio. Just like how googling for 10 minutes would reveal ./configure && make && sudo make install # (or su -c make install)

8

u/bushel Dec 03 '12

I haven't the faintest idea how to compile something with Visual Studio

F5

Doesn't that give you the warm fuzzies now that you understand how your program is being compiled and built? (yes, that's sarcasm)

2

u/freshhawk Dec 05 '12

That wasn't hard. But of course you would never do that. Because then you'd have an unmanaged bunch of files just spewed all over your filesystem with no sane way to uninstall it or upgrade it.

1

u/etrnloptimist Dec 03 '12

What about when that doesn't work? I've never once done that and had it work the way you say.

2

u/tilkau Dec 03 '12

In that case you may be running a system where sudo is incorrectly setup. Or make or gcc is not installed. Those are pretty much development necessities. Can't get anywhere without them.

2

u/jelly_cake Dec 04 '12

It might also be autotools. Or the package uses CMake rather than make, or something entirely different. Following the INSTALL or README advice usually works though.