i have responded to zed shaw's drivelhttps://eev.ee/blog/2016/11/23/a-rebuttal-for-python-3/ …
-
-
I think this just bolsters his case further. If it really is 30% after all this time, beginner tutorials won't help.pic.twitter.com/3pQ3L1ldyC
1 reply 0 retweets 3 likes -
the first few years were spent ironing out kinks, and the next few on porting most of pypi
2 replies 0 retweets 0 likes -
admitting that Python made fatal compat mistakes and committing to fixing them (loudly and clearly) is important.
1 reply 0 retweets 2 likes -
i think it's pretty obvious that the transition did not go as smoothly as was intended
1 reply 0 retweets 0 likes -
but every release of py3 has done something to try to improve that, and there's not that much left
1 reply 0 retweets 2 likes -
py3 is finally in a pretty decent place these last few years, and it took a lot of work to get us here
1 reply 0 retweets 4 likes -
what would you have them do, re-break compatibility with python 3 to be more compatible with python 2?
1 reply 0 retweets 1 like -
no, backport more to 2.7, and reverse some of the breaking changes based on the biggest adoption blockers.
1 reply 0 retweets 2 likes -
simple example: restore support for the old-style print statement.
2 replies 0 retweets 1 like
I think this is the most obvious philosophical problem, and the easiest place to start pushing.pic.twitter.com/uKpsqb8z7G
-
-
it was true for 3.0. it's not been true for a while. 3.2 and 3.3 made vast improvements
1 reply 0 retweets 0 likes -
it sounds like you're saying that Django could use the shim strategy we used in Rails 3 with Py2.7 / http://Py3.now ?
0 replies 0 retweets 0 likes
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.