Re:All Python versions less than 3.6 are now EOL
by jeffrallen on Sunday September 13, 2020 @12:59PM
(#24462200)
It's not a crisis. If Python 2.7 works, people will keep using it. The real crisis is all the lost time dealing with porting to Python 3.
[ Parent
| on HN ]
Re:All Python versions less than 3.6 are now EOL
by zamadatix on Sunday September 13, 2020 @01:02PM
(#24462229)
Middle English still works too doesn't mean it's not a problem to try to use it for a new project. Everything has trade offs, both staying on the old AND moving to the new. At some point everyone does move and managing the size of that transitional tail well is part of running a business well. There is not a one stop answer to the problem of when to migrate to the new and stop using the old but "always bleeding edge" and "always what we started with" are unlikely answers for most places.
Re:All Python versions less than 3.6 are now EOL
by BeetleB on Sunday September 13, 2020 @02:22PM
(#24462827)
> The real crisis is all the lost time dealing with porting to Python 3.
You are agreeing with your parent:
> And at that time it will be non-trivial (to say the least) to fix every affected script and the entire downstream dependency chain because — as so many on HN know — Python 3 is a different language.
Why are people choosing 2.7 for new projects when there is a time bomb coming up? Several years ago, you could blame the Python folks for this break, but once 3.3 (or perhaps 3.5) was out, there was no good reason to start new projects in 2.7, especially when it was publicized that the language will be EOL.