Re:Mercurial’s journey to and reflections on Python 3
by mikepurvis on Monday January 13, 2020 @05:01PM
(#22039207)
I feel like "from __past__" would have allowed projects to get to the point where they were "on Python 3" much sooner, though.
The mentality would have been "we're on Python 3, and we have a long tail of cleanup to do excising from-past out of our codebase" rather than "we and our users are all still on Python 2 but we thiiiiink our code is mostly using constructs that are Python 3 safe. We get a green CI checkmark, anyway, but who really knows."
Hell that's essentially what ended up happening over time, as past features got reintroduced (the `u` prefix, bytes.__mod__, `callable` being reintroduced, `range` being improved, …), as well as the serious Python3-ification of the Python2 branch that was 2.7.