> That’s much more disruptive than the python 2 to 3 migration. Yet Python 2 to 3 started in 2008 - 12 years ago, and is still not “done” in any meaningful sen

> That’s much more disruptive than the python 2 to 3 migration. Yet Python 2 to 3 started in 2008 - 12 years ago, and is still not “done” in any meaningful sense. If I think back to 12 years after the intel OSX transition - 2018 - I can’t think of a single outstanding issue, whereas I bash into python 2 vs 3 literally every time I touch it (and therefore mostly choose not to).