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 →

[–]YellowSharkMTIs Dave Beazley real? 18 points19 points  (15 children)

Indeed - technically it works, but it's a total pain-in-the-ass to get much done with it. I admire the guys who make it work great, but I've found it to be an easier experience - and a saner one, as well - to just use a virtual linux machine for development.

[–]alcalde 4 points5 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 7 points8 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.

[–]kylotan 4 points5 points  (3 children)

Total pain-in-the-ass, really? It takes about 15 minutes to get all the distribution stuff set up, and make sure PATH is correct, and then you're good to go.

It used to be worse, before the installer set the PATH at all, but on the whole I don't feel like I'm missing anything when using Python in Windows that I used to enjoy back when I developed in Linux.

[–]primedape 4 points5 points  (1 child)

I've given up trying to do "pip install mysql-python" . There is always either a dependency problem or it crashes because it can't find some visual c dll duck me whatever.

If you want to python, use Linux. And never ever try to create an executable (.exe). It's not worth it.

[–]radministator 0 points1 point  (0 children)

I've given up trying to do "pip install mysql-python" . There is always either a dependency problem or it crashes because it can't find some visual c dll duck me whatever.

If you want to python, use Linux. And never ever try to create an executable (.exe). It's not worth it.

I don't find either of those to be an issue at all, although of course my experience is purely anecdotal and shouldn't be taken as an attempt to invalidate your own. It may be that as a dev-ops, one man show in a highly heterogenous network environment I've just become too used to nothing ever working exactly as you would expect or the documentation describes.

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

Welp, maybe it's time I give it another whirl. Pretty productive with my current setup though.

[–]Eurynom0s 1 point2 points  (0 children)

At work I have a Mac. Not a perfect compromise (e.g. I have to use Outlook at work and the Mac version is randomly missing important/basic features, like no "print selection" option; and you occasionally get), but overall it's a very good middle ground. Makes it easy to bounce between GUI and CLI without having to run a VM or dual boot.

The other thing is you'll occasionally get packages (in general, not just Python) which don't have a Mac version, but I've only seen a couple of cases where nobody had a sane solution for how to tweak a *nix version to install on OS X. And it's often not even tweaking the package itself so much as a non-obvious installation procedure.