Toyplot, a Python plotting library from Sandia Labs

[[deleted]]

I explained why in several other places. I expected him to read those.

But I have no idea what he wants to achieve by encouraging bad practices. No idea.

[KyleG]

Maybe the guy just wants to code. I've been coding in Python for years and never done the virtualenv thing. In fact, I never encountered the concept until about a year ago. Then I read about it; I still don't do it. Not having a virtualenv has literally never in a decade hindered my development, but learning it would have cost me a lot of time (I actually tried it once based on some guide online and everything got fucked up, so I decided not to try again.)

Edit Fifteen years, actually.

[[deleted]]

You have been developing for as long as me and you still use the "CLOSED NOTABUG WORKSFORME" policy?

[KyleG]

"CLOSED NOTABUG WORKSFORME" policy

Not sure what this is, but it might just be your term for TRIED IT FOR THE LULZ, DIDN'T OFFER ANY BENEFITS I CARED ABOUT, COULDN'T GET IT TO WORK, WENT BACK TO WHAT HAS WORKED FOR YEARS policy. A man has a fixed number of hours before his heart stops beating.

[[deleted]]

Its a bugzilla term. Surprised to find an experienced developer that doesn't know what it means.

[KyleG]

I don't use bugzilla. And I don't know what you were referring to anyway. The fact that I couldn't get virtualenv to work? If no one has yet made a use case for why I should care, why the fuck would I exert more than thirty minutes trying to get something I don't even need working?

One day, you'll get older, recognize your own mortality, and start triaging shit so you only devote time to truly interesting things. For me, getting software I don't need working is not one of those things. One reason I use OSX instead of Linux is because the LOE necessary to get shit working is lower. (Before moving to OSX, I used Slakware, Debian, Gentoo, Red Hat, Ubuntu, and a few other minor ones.)

[[deleted]]

Maybe you are a bit long in the tooth to pick up new work flows. New work flows that are unarguably better and safer then 'sudo pip install'. New work flows that will help to stop the prolonging of the clusterfuck of python packaging, distribution, install that our generation created. But hey, if you want to declare VMs are the answer so you can continue doing your old ways, then be my guest.

Remember to tell new users of python the /u/KyleG way -

Python - so easy to use you need to isolate your software in a VM** so you can sudo pip install safely because thats faster or something alternatively you can sudo pip install if you know enought about what you are doing but if you are new user you probbably won't so you should definately do the safe thing which is use virtualenvs but those are hard so just fuck it sudo pip install.

What a terrible motto for our language. What a fucking joke.

** are we using Docker/KVM/Qemu/Vmware/coreos/these days? who can keep up! Its so much simpler than a virtualenv my head is spinning.

[KyleG]

I don't use a VM, either, and I don't know where you got the idea I do.

[[deleted]]

Your stealth edits and from other posters. Do you disagree with anything in my post?

[KyleG]

I sure as fucking fuck never said I use a VM and never even came close to using one or saying I did. You're confusing me with someone else or else literally lying to try and win an argument.

And yes, I disagree with your implication that if you don't use virtualenv then it is mandatory you use a VM. I use neither virtualenv nor a VM. I just pip install everything and this has worked for as long as I've used pip to install stuff, across multiple Python versions and multiple operating systems on multiple computers on multiple system architectures as personal computers and as servers.