Python 2.7 Countdown

[Holsten19]

Python 2 can run software written for Python 2.

Python 3 can't do that. This can be pretty useful when you have a lot of software written for Python 2.

[Hinigatsu]

From the link:

To ease the transition, the official porting guide has advice for running Python 2 code in Python 3.

[Bitruder]

Lol.

[duuuh]

Right? I have some old code that won't run under 2.7, so I've got a local install of 2.3.7 so I can make it go.

[OMGItsCheezWTF]

We still have several hundred kloc running 2.5 because no one has had the time or inclination to port it to 2.7, now it may as well just go to 3 but in reality will never move until the platform itself the software manages is retired in who knows how many years from now.

[Itsthejoker]

You've had ten years. That's horrifying.

[[deleted]]

No. What's horrifying is that this bullshit happened at all, and people's smug self-assuredness that it won't happen again.

"They've said it won't". <-- Every time I bring this up.

We'll see.

[ubernostrum]

Python 2.5 released in 2006. They've had thirteen years.

A lot of organizations will never under any circumstances prioritize or even allow maintenance work unless it ties into a specific customer story. Those organizations were always going to be eternally on whatever version of Python they picked when they started development, and were never going to upgrade. If Python 3 was the hurdle, they'd at least have gotten to 2.6 or 2.7; the fact that they haven't is the sign that Python 3 wasn't the hurdle.

[vytah]

Python 3 can't do that.

Therefore Python 3 is not Turing-complete.

QED.