Extend Python 2.7 life till 2020
61–70 of 286 posts
Re: Extend Python 2.7 life till 2020
#62Earlier quoted context omitted.
Guido's or yours opinions are irrelevant. If people have a lot of code for Python 2.7 and have little incentive to migrate to Python 3, then they'll stick with Python 2.7.
It's just prolonging the inevitable. Discontinuing support for python 2.7 may give people the spark they need to finally suck it up and migrate their code. But hey, if it's supported another 5 years, why bother.
Re: Extend Python 2.7 life till 2020
#63This is a result of some not so optimal design decisions in the past. I remember, when Py3 first came out, everything was incompatible -- unnecessary incompatibilities like the u" notation for Unicode string literals that was dropped. Unnecessary incompatibilities in the C-extension-module implementation layer. And so on. The list of incompatibilities was just huge. Later several of them where dropped, like the strin…
> unnecessary incompatibilities like the u" notation for Unicode string literals that was dropped I mean a hard difference between a string and bytes and strings being utf-8 by default seem to be a necessary (and good) reason?
Re: Extend Python 2.7 life till 2020
#64Oh for god's sake. Kill the damn thing already. PHP 4 to 5 was a massive leap compared to Python 2 to 3, but they actually made that leap!
Re: Extend Python 2.7 life till 2020
#65I just got back into some Python programming after a 2+ year hiatus from the language. I'm stunned that this 2.x vs 3.x debate is still happening and that 99% of all libraries in use * haven't been converted to 3.x. I like the language, but ... damn... If it weren't for the scikit/numpy stuff, I'd stick with Ruby. The Ruby community seems much less fragmented and wants to see the language move forward. It helps a lot…
Where do you get that many libraries that aren't converted? Most, at least the ones still under development, are.
Re: Extend Python 2.7 life till 2020
#66I still want to see a Python 2 fork getting the care it deserves. I don't trust the motivations of its current developers.
Re: Extend Python 2.7 life till 2020
#67Earlier quoted context omitted.
It's just prolonging the inevitable. Discontinuing support for python 2.7 may give people the spark they need to finally suck it up and migrate their code. But hey, if it's supported another 5 years, why bother.
If people have real compatibility problem to migrate to Python 3, harsh policies will do nothing about that. If I'm forced to rewrite my app I may as well rewrite it in Ruby, Go, Java, or whatever. Especially, if Python developers will prove to be aggressive about compatibility. Why would I migrate to Python 3, just to be forced to rewrite everything in Python 4 next time?
There also isn't really anything as drastic as the bytes/strings/Unicodes left to change.
(But these are better answers to worries about Python3 than they are answers to porting 2.x code bases)
Re: Extend Python 2.7 life till 2020
#68This seems weird to me. Won't this cause a fork in Python at some point, where the 2.7 developers continue on 2.8 or rename it entirely, and another fork continues on what is now Python 3?
Re: Extend Python 2.7 life till 2020
#69Wow I'm very disappointed. I keep making the effort to transition more to 3, but am frustrated to see so many dependencies only work with 2.7, and thus maintain both libraries. I am tired of this limbo.
I don't think it's entirely fair to call people who don't upgrade lazy or scared. However, it's really not that hard at all these days. Most packages are ported, and there are many success stories who have documented all the hard bits.
Re: Extend Python 2.7 life till 2020
#70Anyone know if RHEL 7 will ship with Python 3 in the base, even if not default? That could go a long way to boosting Python 3 adoption. I know it's in SCL, but that lacks convenience for a lot of users.