targeting 2.7 and 3.3/3.4+ is orders of magnitude easier than 2.5+ and 3.0+
-
-
looks like they just aliased buffer to memoryview, which isn't right in general since the api changed a bithttps://github.com/django/django/blob/master/django/utils/six.py#L871 …
-
there's a lot to learn from the JS community here. Polyfills but also shims (starting with jQuery) bridged a lot.
-
Django is on its way back to being py3 only and the default in py3 was not "breaking is okay"
-
porting to py3 and single code base is pretty easy because of a resistance to making breaking changes except where warranted
-
that simply wasn't the POV of the core team at 3.0 and took a bunch of releases to move in that direction.
-
i can't read their minds but it's entirely possible that they just overestimated the effort required
-
then some common pain points became obvious once people started actually porting. that's why 2to3 says what it does too
-
err, /under/estimated
End of conversation
New conversation -
-
-
still, that's not really an argument for the melodramatic assertion that py3k is Dead Man Walking
-
I didn't agree with Zed, but I did say that the impression has solidified and *something* needs to change
-
it's /been/ changing
-
you have a news hook now, so it's a good time for a statement. As an outsider, I think a little humility would go a long way.
-
like i said i have nothing to do with core development
-
maybe someone's watching... :)
-
always watching... for my part i wrote https://eev.ee/blog/2016/07/31/python-faq-how-do-i-port-to-python-3/ … and https://eev.ee/blog/2016/07/31/python-faq-why-should-i-use-python-3/ … which i hope have helped a bit
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.