(i don't expect to /avoid/ his piercing gaze, especially if i write what i want to write, but geez y'all)
-
-
i think it's pretty obvious that the transition did not go as smoothly as was intended
-
but every release of py3 has done something to try to improve that, and there's not that much left
-
py3 is finally in a pretty decent place these last few years, and it took a lot of work to get us here
-
what would you have them do, re-break compatibility with python 3 to be more compatible with python 2?
-
no, backport more to 2.7, and reverse some of the breaking changes based on the biggest adoption blockers.
-
simple example: restore support for the old-style print statement.
-
new-style print is already supported in 2.6+ and is one of the easiest things to translate automatically
-
futurize will do it for you and add the requisite __future__ import as well
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.