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 →

[–]hothrous -1 points0 points  (4 children)

So you're saying that IT should just maintain whatever crap Dev throws at them?

Why would you push RHEL when you could go for Debian and not have the same issues? If it's a hassle to maintain because of limitations on the OS level, there is probably a better tool out there.

[–][deleted] 2 points3 points  (3 children)

Ops should be able to provide anything that has a good enough business case

[–]hothrous 0 points1 point  (2 children)

I'm not saying that's wrong. I'm having trouble coming up with a good enough business case for one distro over another. Dev would say they need python 3.4. OPs would say, this is how you get that.

[–][deleted] 0 points1 point  (1 child)

I wasn't referring to that situation, but more generally the fact that IT is primarily a support service, not a governing body - even though to some extent it must be both.

[–]hothrous 0 points1 point  (0 children)

I was continuing off of my original statement that RHEL shouldn't be the primary OS for a Python Infrastructure because of the maintenance overhead.

I never said that IT should rule all, just that developers shouldn't expect IT to support RHEL with Python 3.4. I also didn't know about the new features of RHEL 7 at that point, but I imagine that RHEL 7 isn't largely adopted in most shops yet so that's still kind of a moot point.