Sunsetting Python 2

Re:Sunsetting Python 2 by protomyth on Monday September 09, 2019 @02:57PM (#20921143)

The GP post missed the fundamental difference between keeping COBOL running and keeping Python 2 running. Python 2 was also PSF's interpreter. IBM handling a COBOL upgrade like PSF handling the 2-3 transition would be unacceptable.

[ Parent | on HN ]

Re:Sunsetting Python 2 by price on Tuesday September 10, 2019 @05:03AM (#20926322)

> IBM

> PSF

These are two very different kinds of institutions!

People who need COBOL support from IBM are paying a lot of money. Giant piles of money can get you many kinds of help that people won't volunteer to do for free... among them, maintaining ancient software in amber.

If you need Python 2 support and you are willing (and able) to pay the kind of money that IBM's customers pay for COBOL support, you'll be OK. For a start, Red Hat (aka also IBM!) shipped Python 2 in RHEL 8, which means they'll be supporting it until 2029 at the earliest.

[ Parent | on HN ]

Re:Sunsetting Python 2 by protomyth on Tuesday September 10, 2019 @11:16AM (#20929140)

To circle back to the original point, no COBOL committee would break commonly running COBOL programs like the Python 2-3 transition. Using COBOL in an example with Python is just wrong. Maybe the break is justified, maybe it isn't, but some languages do a lot of work to make sure things continue to work.

[ Parent | on HN ]

Re:Sunsetting Python 2 by WorldMaker on Monday September 09, 2019 @04:37PM (#20922202)

Would PSF exponentially increasing support and maintenance costs for Python 2 into multimillion dollar contracts and bundling over-margined hardware in with the bundle to make it more of an IBM-like transition help?

[ Parent | on HN ]

Re:Sunsetting Python 2 by protomyth on Monday September 09, 2019 @08:27PM (#20924003)

Yep, someone has to pay in one way or another like Red Hat customers on 7, but to say Python has near the life cycle of COBOL is just disingenuous. Old COBOL still runs, but Python 2 programs will not. It really shows what the achievement languages like COBOL, RPG, and Fortran are in terms of longevity and migration.

[ Parent | on HN ]

Re:Sunsetting Python 2 by mynameisvlad on Monday September 09, 2019 @09:54PM (#20924463)

> but Python 2 programs will not

Er, why not? It's not like there's some kill switch in Python 2 that will make it stop working after January 1st, 2020. If it works now, then it'll still work, you're just not guaranteed fixes anymore. At least, not for free. As stated in the article, paid support options exist from several vendors.

[ Parent | on HN ]

Re:Sunsetting Python 2 by protomyth on Tuesday September 10, 2019 @11:12AM (#20929079)

Any software in the modern era that isn't upgraded for new OSes or security patched is dead.

[ Parent | on HN ]

Re:Sunsetting Python 2 by mynameisvlad on Tuesday September 10, 2019 @03:54PM (#20932906)

Ok, sure. To you, maybe. But that's a far cry from saying they won't run anymore.

[ Parent | on HN ]

Re:Sunsetting Python 2 by C1sc0cat on Tuesday September 10, 2019 @06:45AM (#20926799)

You can still run 1960's code today for both COBOL and Fortran - I suspect some Fortan 2 oddities might not work I am thinking of the sense commands

[ Parent | on HN ]

Re:Sunsetting Python 2 by protomyth on Tuesday September 10, 2019 @11:13AM (#20929101)

Probably, but the care the Fortran folks take to not break anything but still evolve a modern language is amazing.

[ Parent | on HN ]