Live data from Hacker News

Extend Python 2.7 life till 2020

hg.python.org

121–130 of 286 posts

Re: Extend Python 2.7 life till 2020

#121
post #7

Earlier quoted context omitted.

Since it's only bug & security fixes for Python 2.7.x from this point on, the momentum to python 3.x will pick up considerably. Python 3 compatibility far outnumbers incompatible packages now: http://python3wos.appspot.com

> the momentum to python 3.x will pick up considerably. People won't leave Python 2.7 for Python 3.x, they'll go to other languages. Python has no right to its users.

bullshit. i have several large Django code bases to maintain and all of them could move to py3 if needed if it wasn't for boto. As soon as they are ready porting boto my next projects will all be py3.

Re: Extend Python 2.7 life till 2020

#122

Earlier quoted context omitted.

Well honestly, python 2* is a lot more convenient to write in a lot of ways, and the benefits of 3 aren't big enough to make up for it for a lot of people/use cases.

> Well honestly, python 2* is a lot more convenient to write in a lot of ways In what way is python 2 more convenient to write? Outside of the rapidly shrinking set of cases where the best approach to a key problem is addressed by a Py 2 only library -- or the case of "I want to deploy on Google App Engine" -- I don't really see how Py 2 is "more convenient".

On both OSX and many Linux distros, Py 2 comes pre-installed but Py 3 does not. If I'm going to write simple scripts that I'm going to give out to people, it's nice not having to worry about them needing to fuck around to get the script to run.

Re: Extend Python 2.7 life till 2020

#123

Earlier quoted context omitted.

> I for one like the 2.x style print function. 2.x didn't have a print function, unless you mean the one from 3 available with a from __future__ import.

In case the grandparent doesn't realize, 2.x has a print statement not function.

I meant function as in functionality. This is really pointless nitpicking.

Re: Extend Python 2.7 life till 2020

#124
post #92

Earlier quoted context omitted.

> I have no use of python 3 You admit you haven't done any research, so you clearly don't have any basis for making that statement.

Nor have I done research on Perl, Scala, etc. Your missing my point. I am successfully getting my things done in Python 2. I do not have any use for Python 3, Perl, Scala, or any other language. I might have in the future, and hey, some language might be better suited to solve the problem - but as long as it's not drastically better the sensible tradeoff is to stick with Python 2.

That philosophy sounds like one that will cause you to wake up one day and realize your skill set is massively out if date.

Python 3, scala, and pearl all give you new ways of solving a problem. You're missing out on a lot of super cool stuff by not exploring! Outside of maybe library support, I see no reason to not to at least check out python 3.

Re: Extend Python 2.7 life till 2020

#125
post #23

Oh 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!

Amongst others, the Mercurial devs talked to Guido during Pycon about the huge porting effort towards Python 3 (with little benefit to the hg codebase). Let's not forget that Python itself hosts its code on http://hg.python.org . And during Guido's keynote (which should be online tomorrow) he said his own Dropbox has a huge Python 2.x codebase live on the servers which is difficult to migrate. He didn't take the deci…

Captain hindsight then to the rescue, py3 shouldnt have existed and a 2.8 should habe been made.

Re: Extend Python 2.7 life till 2020

#126
post #7

Earlier quoted context omitted.

Since it's only bug & security fixes for Python 2.7.x from this point on, the momentum to python 3.x will pick up considerably. Python 3 compatibility far outnumbers incompatible packages now: http://python3wos.appspot.com

> the momentum to python 3.x will pick up considerably. People won't leave Python 2.7 for Python 3.x, they'll go to other languages. Python has no right to its users.

Considering Py2.7, Py3 is actually an "other language". Why would all these people throw out their Python expertise?

Re: Extend Python 2.7 life till 2020

#127

Earlier quoted context omitted.

Well honestly, python 2* is a lot more convenient to write in a lot of ways, and the benefits of 3 aren't big enough to make up for it for a lot of people/use cases.

> Well honestly, python 2* is a lot more convenient to write in a lot of ways In what way is python 2 more convenient to write? Outside of the rapidly shrinking set of cases where the best approach to a key problem is addressed by a Py 2 only library -- or the case of "I want to deploy on Google App Engine" -- I don't really see how Py 2 is "more convenient".

[deleted]

Re: Extend Python 2.7 life till 2020

#128

I see many comments talking about how this will slow down the migration process. But I don't think the situation is that bad. Most of the py3 wall of superpowers is now green ( https://python3wos.appspot.com/ ) with boto, mysql-python, nltk, python-openid being some of the rare few in terms of not having great py3 alternatives. And most of these have ports on the way already. So one interesting effect of this is that…

Many reds on the list also have py3 support in branches or forks for unmaintained ones like suds.

Re: Extend Python 2.7 life till 2020

#130
The lesson here is that it's important to "sell" new versions of anything. You can't just expect people are going to upgrade because it's the new hotness. Older versions of your own software are often your biggest competitor. (See also: Microsoft and Windows 8).
Post reply on HN