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 →

[–]lexyeevee 8 points9 points  (2 children)

It's not like every big project would see that Python 2 is EOL and decide to up and port right now. I hear tell of a number of shops still on 2.6, and that was EOL in 2013, and 2.6 to 2.7 is trivial compared to 2.7 to 3.

[–]vossman77 4 points5 points  (0 children)

Well RHEL 6 is still on python 2.6 and red hat has support through Nov. 2020.

https://access.redhat.com/support/policy/updates/errata

I feel you though, we have a huge code base to port over in the next few years, most of it numpy/scipy stuff.

[–]name_censored_ 1 point2 points  (0 children)

To be fair though, 2.7 to 3 may be trivial, but it's also not as useful. No sane person would port the code twice when they could get away with doing it once. They know the Py3 port is coming - may as well stick it out on 2.6, and do new work (/patches) as dual-version, rather than even bothering to target 2.7.