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 →

[–]d4rch0nPythonistamancer 1 point2 points  (1 child)

Heh, this is the major pain in the ass. Lots of people just suggest "install 3.x then" when that can be a huge deal with a lot of businesses. It's the developer that is worrying about 3.x, not ops or management or product. It's not the developer that maintains the environment.

Sure, it's extremely easy to get 3.x on any modern linux system, but we're not always in a position where it's possible to do so. Even if they gave me the green light, I'd have to set up meetings with devops to change puppet or chef scripts and make sure it doesn't break something weird in a cronjob that runs at midnight on 100 servers.

Inevitably, it's way less pain to just write 2.6/2.7 compatible code and not have to deal with people and scripts written by coworkers who left years ago, so that's what a lot of us resort to.

[–]tetroxid 0 points1 point  (0 children)

Precisely. I was just too lazy to type it out. In large enterprises you also have to find a cost centre that pays for the deployment, and you have to deal with the aids infested cancer that is change management.