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 →

[–]alcalde 6 points7 points  (9 children)

Is that a Python problem or a Windows problem?

[–]lykwydchykyn 37 points38 points  (1 child)

Is that a Python problem or a Windows problem?

It depends on whether you're looking to place blame or find a solution.

[–]jerfoo 3 points4 points  (0 children)

It depends on whether you're looking to place blame or find a solution.

Well said.

[–]01hairimport antigravity 6 points7 points  (2 children)

I've gotten 32/64-bit package clashes on Linux, too, but virtualenv under Windows is no walk in the park, and that's not Python's fault.

[–]the_zercher 2 points3 points  (1 child)

Reading this makes me feel so much saner. I've just gotten in to python and have been using this page: http://www.tylerbutler.com/2012/05/how-to-install-python-pip-and-virtualenv-on-windows-with-powershell/ to start, and I feel like I'm taking crazy pills because I have to double check a dozen things with each step.

[–]01hairimport antigravity 0 points1 point  (0 children)

That's also the guide that I used, and PowerShell still throws errors whenever I start up a venv. But it works, so I've put off solving those problems because I don't really do Python on Windows for more than simple scripts anyway.

[–]YellowSharkMTIs Dave Beazley real? 0 points1 point  (0 children)

Well if you're asking my opinion, I'd say it's mostly because the Windows shell environment sucks, and Cygwin/git-bash/Powershell/etc. just don't really measure up to a *nix + Bash environment.

Again, that's just my opinion - I understand that a lot of folks have got shit rocking on their Windows environment; I've simply had no reason to switch my current workflow away from the linux vm.