I won't speculate anymore, but would love to hear from them. 3/3
-
-
https://wiki.python.org/moin/PortingPythonToPy3k … also, why are Django's custom additions to six not upstreamed?
-
according to the docs, their additions are for "internal use only" https://docs.djangoproject.com/en/1.10/topics/python3/#module-django.utils.six …
-
right but the same shims would likely be useful for other projects, and help aid the transition.
-
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.
- 3 more replies
New conversation -
-
-
Already written: http://python-notes.curiousefficiency.org/en/latest/python3/questions_and_answers.html … Porting entire Linux distros takes a while, and lots of folks use the system Python.
-
There's also http://developers.redhat.com/blog/2014/09/17/why-python-4-0-wont-be-like-python-3-0/ … & http://developerblog.redhat.com/2014/09/09/transition-to-multilingual-programming-python/ … specifically about the disruption from the Unicode change.
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.