Python 2.8? • Hacker News Board

Re: Python 2.8?

#71

Post by gspetr » Mon, Jan 23, 2017, 1:40 AM UTC

TylerE wrote: post #66

MattConfluence wrote: post #61

Earlier quoted context omitted.

> Giving people more time to transition is going to benefit some projects. Python 3 was released in December 2008. Python 2.7 was released in July 2010, and was given 5 years of support which was then extended to 10. Those people who have not transitioned yet have not done so because of lack of time. They might have valid reasons for delaying, but time is not one.

I disagree. When your dev team is totally busy working on features that customers are actually paying for, there is less than no business case for porting to Py3.

In 2017 you may be right.

In 2020? There will certainly be a business case once you get hit with an RCE in 2.7 because there will be no new security patches.

Re: Python 2.8?

#72

Post by sametmax » Mon, Jan 23, 2017, 6:22 AM UTC

hueving wrote: post #70

sametmax wrote: post #52

Earlier quoted context omitted.

Well, another issue is that there are carrots, but they are tough to sell. I have been using Python 3 for 2 years now in production, and I would never want to go back to Python 2. Benefits include: - less boilerplate. Automatic super(), no object inheritance, yield from, generalized unpacking, keyword only args, less itertools import, no need for __future__, f-srings, etc. Basically my code is shorter and faster to w…

Good points, but error handling and less boilerplate are mostly moot once the code is already written, which is what makes them not great carrots for switching projects.

Yes it's more "invest now, get the next iterations of your project in a better shape". And it's not as appealing as "invest now, get 30% speed up now".

Re: Python 2.8?

#73

Post by oliwarner » Mon, Jan 23, 2017, 11:21 AM UTC

freyir wrote: post #57

I suspect there's a sudden push for "Python 2.8" from some of the 2.x holdouts because it's becoming increasingly obvious that the wider community is coalescing around 3.x. I feel a bit sorry for people stuck on large Python 2 projects and who can't make the jump, but there's a very vocal minority in this group that wants the rest of the world to be held back along with them.

For those people genuinely "stuck" I can certainly understand wanting to prolong the life of 2.7 past 2020. It keeps legacy products secure and working without having to retool them onto 3.x, which really is a big job. Why not. The core python team is unhappy keeping it on life support but why couldn't somebody else?

But this "2.8" is about adding 3.x language features onto 2.7, essentially declaring a brand new language standard for new development. People who want this aren't saying they don't want to upgrade, they're saying they want to stay on 2.x forever. That seems perversely stubborn to me.

Re: Python 2.8?

#74

Post by unixhero » Tue, Jan 24, 2017, 8:06 AM UTC

Tenobrus wrote: post #22

unixhero wrote: post #16

Earlier quoted context omitted.

The problem is some of the massive python modules that cannot be ported from 2.7 to 3 .x

Sure there are some, but several lists (for example, http://py3readiness.org ) show that over 95% of very popular packages support Python 3, and some only support Python 3. At this point while you might need 2 for some very specific purposes, 3 has the majority of important packages and new development.

I stand corrected. I realize that it was 4 years ago, since I tried to learn Python ... And at that point in time key libraries, which I for instance read books to learn, twisted, was 2.7 only ...