except that occasionally someone who stopped paying attention in 2009 appears to declare py3 a disaster, so the sentiment persists
-
-
Replying to @eevee
I think a strong statement acknowledging how bad the original fuckup was and talking through this would help.
2 replies 0 retweets 2 likes -
https://wiki.python.org/moin/PortingPythonToPy3k … also, why are Django's custom additions to six not upstreamed?
1 reply 0 retweets 1 like -
Replying to @wycats
according to the docs, their additions are for "internal use only" https://docs.djangoproject.com/en/1.10/topics/python3/#module-django.utils.six …
1 reply 0 retweets 1 like -
Replying to @eevee
right but the same shims would likely be useful for other projects, and help aid the transition.
2 replies 0 retweets 1 like -
Replying to @wycats
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 …
1 reply 0 retweets 0 likes -
Replying to @eevee
there's a lot to learn from the JS community here. Polyfills but also shims (starting with jQuery) bridged a lot.
1 reply 0 retweets 2 likes -
Django is on its way back to being py3 only and the default in py3 was not "breaking is okay"
2 replies 0 retweets 2 likes -
porting to py3 and single code base is pretty easy because of a resistance to making breaking changes except where warranted
3 replies 0 retweets 0 likes -
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 replies 0 retweets 1 like
I'm happy to see that it looks like that era is over (I'd missed some details, thx @eevee!) and think a strong stmt would help
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.