4 ms·
> The author's suggestion of permitting a certain set of "from __past__" imports seems especially astute. Hell that's essentially what ended up happening over
by masklinn 7y ago
> The author's suggestion of permitting a certain set of "from __past__" imports seems especially astute.
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.
- mikepurvis 7y agoI 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."