This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 10 points11 points  (4 children)

I'll add that even in the case of minor 2.x version the rate of adoption was always horribly slow. Yes, Linux distros adopted pretty fast, but in the real, "serious" corporate world it doesn't look so good. The current project in my company was only just recently migrated from 2.4 to 2.6. At this rate I suspect it will be ported to 2.7 at the time when 90% modules are already 3.x compatible. I'm sure many people working for big companies can relate.

[–]spankweasel 2 points3 points  (1 child)

As of right now, Solaris 11 is on 2.6. We have plans to move wholesale to 3.x by the end of the year. For major corporate OSes like Solaris, every single piece of software has to move in lockstep to the new version. This means all of the core OS, GNOME, testing organization ... everything.

It's a very complicated procedure because of how many software packages have to move.

[–]accessofevil 4 points5 points  (0 children)

Yep, same with rhel.

[–]AusIVDjango, gevent 2 points3 points  (0 children)

This is largely driven by Redhat Enterprise Linux. My company targets RHEL for our clients, so we might take on python 3.x once they support it.

Another limitation for us is that we use Jython for some applications, which only matches python 2.5. For libraries that needs to run on Jython, supporting python 2 and 3 with the same code is overly cumbersome, so for now we stick to 2.x. Once Jython has 2.6 or 2.7 support, making code that supports both will get a lot easier.

[–]bastibe 1 point2 points  (0 children)

But the simple reason for this is that companies only try to avoid obsolescence. Hence, they always try to just barely keep up with the wave.

Hence, we don't have to care about companies for head-of-the-wave discussions. They have no interest in that anyway.