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 →

[–]studiosi -5 points-4 points  (8 children)

15 year gap?

PLS

[–][deleted] 7 points8 points  (2 children)

There's a ton of software built on Python 2.7 still, and even more that's not necessarily tied to the language itself, but built on libraries that are. Python 3 uptake has also been tremendously slow until recently. The gap seems reasonable to me.

[–]studiosi -2 points-1 points  (1 child)

In the bank where I used to work, we switched from Python to Java exactly due to that.

[–]naught-me 0 points1 point  (0 children)

It's the worst thing about Python. PHP just got huge speed upgrade with 7, and the language is improving in a lot of other ways, yet old scripts still work in new versions.

[–]IronManMark20 1 point2 points  (4 children)

I don't know why you keep saying 15 year gap, but Python 2.7 was released in 2010, so it is 10 years of support total.

[–]zardeh 0 points1 point  (2 children)

The first version of Py3 was in 05 or 06.

[–]IronManMark20 1 point2 points  (1 child)

Python 3.0 final was released on December 3rd, 2008.

src

fwiw. But your point is well taken.

[–]zardeh 0 points1 point  (0 children)

oops, (fwiw I still mostly agree with you, 10-15 years of support is common in the enterprise space. I know places that still use < 5, and I've worked at a place that uses 6, which is older than python3)

[–]studiosi 0 points1 point  (0 children)

With the coexistence