Re:How we rolled out one of the largest Python 3 migrations
by Longhanks on Wednesday September 26, 2018 @02:51AM
(#18073356)
It'll be very interesting to see what happens with the next macOS when Python 2 will be EOL (which is roughly 3 months after its release). The upgrade to Python 3 is long overdue.
[ Parent
| on HN ]
Re:How we rolled out one of the largest Python 3 migrations
by CJefferson on Wednesday September 26, 2018 @03:10AM
(#18073454)
Python being EOL sounds scary but actually won't matter to Apple. They already apply custom patches, they can carry on running python 2.7 forever, with minor bug fixes where really required.
Re:How we rolled out one of the largest Python 3 migrations
by guitarbill on Wednesday September 26, 2018 @04:33AM
(#18073939)
> they can carry on running python 2.7 forever
would they do this? does anything macOS internal depend on python 2.7?
Re:How we rolled out one of the largest Python 3 migrations
by varenc on Friday September 28, 2018 @07:28PM
(#18097814)
the `xattr` terminal command relies on the system installed Python, though this seems to be the only example.
If you look at the source in `/usr/bin/xattr` it does some work to deal with different versions of Python. All the work ultimately gets handled by the xattr module preinstalled with the system Python. This module has Apple's copyright in it and is different than the `xattr` module on pypi.
Wonder how this Python one-off in macOS came to be.