Re:Sunsetting Python 2
by tannhaeuser on Monday September 09, 2019 @04:07AM
(#20916122)
I'm no Python insider, but Google has quite a lot of projects based on Python 2, including build scripts for recently released software, so I'm guessing they could at some point maintain their own Python 2 branch (which, again, I'm guessing is much less work than porting a huge amount of script code over to 3 for no material benefit).
[ Parent
| on HN ]
They already have one - look in their type checker repo for patches that add certain Python 3 features (type annotations) to Python 2.
That's sort of hilarious... What are the incentives that prevent Google from upgrading their python 2 scripts to python 3? I guess it's more productive globally to stick with a supported version of Python 2.
Re:Sunsetting Python 2
by tannhaeuser on Monday September 09, 2019 @03:48PM
(#20921706)
Not the one you're responding to, but there are many cases where Python is used in the role of a shell script replacement eg. build scripting and test suite automation that wouldn't benefit from migration and, in fact, would suffer from half-assed migration attempts with little or no real-world testing.