5 ms·
>You had almost 15 years of warning from initial announcement to eol. Why should I have to do labor to fix things that already work?
by ornxka 6y ago
>You had almost 15 years of warning from initial announcement to eol.
Why should I have to do labor to fix things that already work?
- CogitoCogito 6y ago> Why should I have to do labor to fix things that already work? You don't right? Python 2 still works.
- michaelmrose 6y agoMaintaining python2 and python3 forever in perpetuity wouldn't be free either. Why should they provide free labor in perpetuity so that you need no provide any? In theory if there was sufficient need the entire community of python2 users could collectively fund said support but I don't see how they can demand it for free.
- takeda 6y agoYou don't have to it's not like PSF made Python 2.7 stop working on January 1st 2020.
- isbjorn16 6y agoYou don't need to, provided you're willing to also maintain a Python 2.x fork on your own instead, or willing to pay someone else to do it for you, or willing to risk no more patches to the interpreter. You do you, boo.