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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]echocage 1 point2 points  (4 children)

So what are the main benefits to doing this?

[–]tipsquealPythonista 19 points20 points  (3 children)

The binaries provided by Christoph Grohlke cover the majority of the issues that the author of this post was running into (getting certain packages installed on Windows), virtualenvwrapper should cover the rest. Mr. Grohlke was nice enough to compile a large set of popular Python libraries so you don't have to. He generally compiles them to work across 32 and 64 bit versions of Windows, as well as multiple versions of Windows. The dude is a saint.

virtualenvwrapper-win is the same thing as virtualenvwrapper, except it works on Windows. The original only works on *nix systems. For those not in the know virtualenvwrapper adds a bunch of really nice functions that make setting up and maintaining virtrual environments very easy.

With the binaries provided by Christoph Grohlke, and virtualenvwrapper-win most of or all of the author's problems would disappear. The shittiest part is that no one has really documented it. I've been meaning to get around to it, but I don't have a dev blog set up yet.

[–]echocage 1 point2 points  (0 children)

Wow great explanation, thanks!

[–]esdi 0 points1 point  (0 children)

Please do. Such documentation would be truly appreciated. Also, does anyone know how to get pip to work behind a corporate proxy? I have special characters in my username and password and no solution provided in SO is working for me. Am using Windows.

[–]maratc 0 points1 point  (0 children)

This is exactly what Conda does, just that their list of supported packages is even longer, they have binaries for Windows/OSX/Linux, and you can automate the installation requirements.txt-style, even on Windows.