it's just a sprinkling of microscopic issues you wouldn't think about, like a class named "nonlocal" (now a keyword in py3)
-
-
most of pypi works with python 3 now. even twisted is on its way. everything is great.
1 reply 1 retweet 0 likes -
except that occasionally someone who stopped paying attention in 2009 appears to declare py3 a disaster, so the sentiment persists
1 reply 0 retweets 3 likes -
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 -
still, that's not really an argument for the melodramatic assertion that py3k is Dead Man Walking
1 reply 0 retweets 0 likes -
I didn't agree with Zed, but I did say that the impression has solidified and *something* needs to change
1 reply 0 retweets 0 likes -
it's /been/ changing
2 replies 0 retweets 0 likes
maybe so. a clear "whoops, we messed up, here's what we did to improve" would be better than "y u no upgrade"
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.