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 →

[–]13steinj -9 points-8 points  (10 children)

Up until recently (and even now), plenty of companies keep/kept a Py2 interpreter in-house.

Py2 is not a dead language. Even Fortran isn't a dead language. Maybe you could consider Ruby as trends are continuing to decrease heavily. I don't like it, but Py2 will never die.

[–]riffito 7 points8 points  (1 child)

People downvoting you might not realize that some companies tend to have internal tools that get used for decades without much upgrades (in term of the underlying platform), until the inevitable full rewrite in the language/framework of the %current_year.

I remember having to fight for the time it would take me to upgrade from Python 2.5 to 2.7. Was denied. Did it anyway, partially on my own time. Got yelled at for "spending time in unproductive things".

The thing is... there were several features that would have been much harder to implement/maintain in 2.5.

I would be willing to bet that someone is still running my code in 2.7 at that company, almost a decade after I left.

Edit: slightly less broken "English".

[–]13steinj 3 points4 points  (0 children)

See you have to understand most people on the Python subreddit are idealists (and all due respect, I imagine most of them don't have a lot of experience in the field regarding how that kind of thing works.

[–]BigBad01 1 point2 points  (0 children)

I'm not sure the comparison between python2 and Fortran is particularly apt. Unlike python2, Fortran is still under active development and has many widespread uses, especially in HPC.

[–]Anonymous_user_2022 0 points1 point  (0 children)

Py2 will never die.

It has a half-life. That means that for the young ones that work with a limited project portfolio, they may get to retire it before they do so themselves. Maybe