undefined | Better HN

0 pointsguitarbill7y ago0 comments

Apple is quite happy breaking and deprecating things between macOS versions, why would some legacy scripts that are already in support only and will be EOL in 2020 change that? Unless they use it internally, why would they spend money on maintaining a Python version at all?

Maybe for e.g. RHEL it makes sense to maintain Python 2 beyond end of life, since they can charge an arm and a leg for companies who have been too lazy or complacent to port and upgrade their stuff, despite clear and generous deprecation timelines. But I don't buy this for Apple.

0 comments

1 comments · 1 top-level

CJefferson7y ago

Just because the Python devs want to declare Python 2 eol, Apple can do what they want.

There are many pieces of software (bash and clang as major examples) where Apple keep custom branches, often of otherwise unsupported versions.

j / k navigate · click thread line to collapse