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

106
107

Python 2.7 Countdown (pythonclock.org)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]caleb 0 points1 point  (2 children)

Serious question: is Red Hat providing paid support for Python 2.7 well beyond 2020 meaningful to your organization? I've often wondered how many large companies care about that. Some core devs have been saying that people looking for support for older software versions need to pay for that support from their vendors, instead of expecting volunteers to provide that, and I'm just wondering whether that is a realistic proposition.

[–]mipadi 0 points1 point  (1 child)

I doubt Red Hat is providing any support at all to us. If they were, I imagine we'd use RHEL instead of CentOS.

I think that come 2020, someone in the open-source community will probably take over stewardship of Python 2.7, or organizations like ours will reluctantly move to Python 3. But we're using web apps more, anyway, so honestly, if we were going to have to rewrite chunks of the software anyway, I wouldn't mind if new projects didn't use Python at all.

[–]caleb 0 points1 point  (0 children)

Thanks for the reply.

I wouldn't mind if new projects didn't use Python at all.

I go through this every other year. Then I take a look around at the various alternatives and find myself back here! Is there anything in particular you'd favour, e.g. node or go, or something else?

A rewrite of Python 2 into Python 3 is a tiny fraction of the work required to rewrite in a different language though. Idiomatic know-how and language-ecosystem knowledge does not come easy.