4 ms·
Just to add some perspective from another language: Ruby had a similar, traumatic rift when transitioning from 1.8 to 1.9. I don't think it's a coincidence that
by danso 11y ago
Just to add some perspective from another language: Ruby had a similar, traumatic rift when transitioning from 1.8 to 1.9. I don't think it's a coincidence that -- like Python 2.x to 3.x -- Unicode-handling was one of the changes...so even though Ruby 1.8 to 1.9 had fewer compatibility breaks than Python 2.x to 3.x, it still pissed off a lot of people.
But what made the community jump, IMO, was the fact that the Rails maintainers announced that they would be upgrading to 1.9 [0]. And since there is a very small subset of Ruby users who don't use Rails, that was the end of discussion.
Is there any library in Python that enjoys as much dominance over the language as Rails does to Ruby? Not from what I can tell...And virtually all of the big mindshare libraries in Python have made the transition (e.g. NumPy, Django)...So I agree with OP that making libraries commit to 3.x-or-else is the way to encourage adoption of 3.x...but I just don't see it working as well as it did for Rails/Ruby. That's not necessarily a bad thing, per se, in the sense that it shows the diversity of Python and its use-cases, versus Ruby and its majority use-case of Rails. But forcing the adoption of a version upgrade is one situation in which a mono-culture has the advantage (also, see iOS vs Android).
[0] http://yehudakatz.com/2009/07/17/what-do-we-need-to-get-on-ruby-1-9/ http://yehudakatz.com/2009/07/17/what-do-we-need-to-get-on-r...
- Freaky 11y agoRuby 1.9 rewarded your upgrade efforts by running twice as fast. There was a lot of enthusiasm to migrate. Python 3 still seems to reward you by running slightly slower. Where's the hook? Marginal improvements to language design are bit of a weak sell for a language that's already pretty nice.
- wbond 11y agoAll of the testing I've done with real-world code has shown an improvement of 10-20% moving from 2.7 to 3.4. I believe 3.5 made some slight further improvements.
- BuckRogers 11y agoIf only CPython3 wasn't completely blown out of the water by Python2's production-ready PyPy. That said, my tests are the exact opposite of what you're claiming- I've been doing the same benchmarks on all the CPython3 releases since 3.2. I think you're the only person I've heard make that claim in fact.
- toyg 11y agoDjango made the transition more than 4 years after Python 3 was released. Flask took a few months less. Requests took more than 3 years. Basically, for the first three years (2009-2012) Python 3 was almost entirely embargoed by the most popular Python projects. The problem was not the lack of monoculture, but that all the strongest projects took their sweet time. (To be fair, it might be that they were lobbying for the compatibility hacks that did land in 3.2 and 3.3, about 2 years after the .0 release.) There was no trailblazer among the big projects. The only real pioneers were the Arch guys, making py3 the default interpreter quite early on; but the popularity of a minor Linux distribution is nowhere near the main projects'. Still today, some of the most prominent leaders on such projects (the_mitsuhiko, kennethreitz etc) are very much Py3-skeptics; but at least the big frameworks have moved on, so everything else is starting to catch up. We just lost 3 years.
- williamstein 11y agoOne Python library with some mindshare that has not made the transition is SageMath (http://sagemath.org http://sagemath.org). We haven't even tried yet (mostly due to lack of funding/time: https://groups.google.com/forum/#!topic/sage-devel/cUVKUx31gME https://groups.google.com/forum/#!topic/sage-devel/cUVKUx31g...). SageMath depends on sympy, so if sympy were to switch to support Python3 only before we do, then I guess we would never update sympy again in Sage.