Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Python 2.7 Countdown

pythonclock.org

Post reply on HN
Print view View original

21–30 of 72 posts

Re: Python 2.7 Countdown

#21

Post by sametmax »

Let's take all a minute to thanks the awesome cpython team. Most of the devs work on it for free. They have very little budget as opposed to corporation backed projects like go, c# or js.

Yet.

The language has helped us since 5 years before java was born. You can find it in websites like youtube and instagram, OS stacks like linux and mac, wall street and NASA analytics, popular GIS, dropbox UI, blender and maya, sublimetext...

Also thanks for having provided almost 15 years and many tools to migrate from 2 to 3. I know few languages that managed such a big update, but none that gave so much to help with the transitions.

Guys and gals, you rock.

And it needs to be said because we hear the people complaining the most loudly. Never all the people that are so grateful for it.

Re: Python 2.7 Countdown

#22

Post by Lev1a »

alergico wrote: post #10

Guess the community (or a company like RedHat) will have to step in and fork 2.7. There is no way that people who haven't switched, will want to switch, unless absolutely forced to (for example: no security patches).

Like with any other system where some old version just won't go away, the ones who absolutely will not switch to Python 3 will eventually (literally) go extinct.

What we can do, as the people who live in the present, is educate programming/python newbies to use the newer/better Python 3, instead of clinging to something that will soon lose official support (for AFAIK good reasons).

Re: Python 2.7 Countdown

#23

Post by filleokus »

euroclydon wrote: post #14
jhanschoo wrote: post #5

Earlier quoted context omitted.

The old school (sandboxed, not containerized) google app engine still only supports 2.7.

I’m just starting a GAE app for the first time ever and I chose what you call “old school”, but they call “standard” because my understanding is that it’s more cost effective in that when you have no traffic, you have little to no costs. Also, standard has start up time of like a second vs minutes for the “flexible” version. Basically standard, with Python 2.7 is a true app engine, where flexible is just a container…

I was using GAE Standard with Python on my last gig for a couple of years, and now I'm using GAE Flexible, and I totally agree with you.

My guess have always been that the naming choice was an attempt at rescuing the somewhat bad PR they had with GAE Standard by "polluting" (improving) the GAE brand with this new thing.

(I was seriously concerned when I was told during the interview that they were using GAE on this job, but reliefed when it turned out to be GAE Flexible. However, I do miss some of the magic provided by Standard, but do not miss Python 2.7 and some of the restrictions.)

Re: Python 2.7 Countdown

#24

Post by mkesper »

cbcoutinho wrote: post #12
bhaavan wrote: post #9

MacOS still ships with Python 2 as the default python.

As it should, 'python' should continue to point to python2 to maintain compatibility between *nix systems [0] [0] https://www.python.org/dev/peps/pep-0394/

From that PEP: It is anticipated that there will eventually come a time where the third party ecosystem surrounding Python 3 is sufficiently mature for this recommendation to be updated to suggest that the python symlink refer to python3 rather than python2.

Re: Python 2.7 Countdown

#25

Post by [deleted] »

alergico wrote: post #10

Guess the community (or a company like RedHat) will have to step in and fork 2.7. There is no way that people who haven't switched, will want to switch, unless absolutely forced to (for example: no security patches).

[deleted]

Re: Python 2.7 Countdown

#26

Post by digi_owl »

ceronman wrote: post #18
alergico wrote: post #10

Guess the community (or a company like RedHat) will have to step in and fork 2.7. There is no way that people who haven't switched, will want to switch, unless absolutely forced to (for example: no security patches).

I can see a company providing 2.7 support afterwards. I'm not sure if RedHat, but if there is demand, I totally see 2.7 support as a viable business, at least for awhile. I think it's unlikely that the community will bring support. Most of the community already jumped to 3.x, and those who haven't will do in the next two years. Also, supporting legacy code is not something that volunteers love to do.

> supporting legacy code is not something that volunteers love to do.

And this is perhaps the Achilles heel of FOSS in the long run...

Re: Python 2.7 Countdown

#27

Post by hansjorg »

Lev1a wrote: post #15
bhaavan wrote: post #9

MacOS still ships with Python 2 as the default python.

AFAIK, Ubuntu does as well (if you mean that you have to write 'python3' instead of 'python' to execute Python3)

It does. Not sure at what Ubuntu version it happened, but they've transitioned to Python 3 as default. Python 2 isn't even present in a default install anymore.

Re: Python 2.7 Countdown

#28

Post by dude01 »

euroclydon wrote: post #14
jhanschoo wrote: post #5

Earlier quoted context omitted.

The old school (sandboxed, not containerized) google app engine still only supports 2.7.

I’m just starting a GAE app for the first time ever and I chose what you call “old school”, but they call “standard” because my understanding is that it’s more cost effective in that when you have no traffic, you have little to no costs. Also, standard has start up time of like a second vs minutes for the “flexible” version. Basically standard, with Python 2.7 is a true app engine, where flexible is just a container…

Yeah I'm still using the "standard" GAE, because it's simpler and still has better features -- but old Python :-(. I'm hoping they will eventually upgrade it, but I don't work there, so who knows?

Re: Python 2.7 Countdown

#29

Post by hungerstrike »

guitarbill wrote: post #16
alergico wrote: post #10

Guess the community (or a company like RedHat) will have to step in and fork 2.7. There is no way that people who haven't switched, will want to switch, unless absolutely forced to (for example: no security patches).

This old chestnut. Yeah, if there's enough people who are willing to pay for it (time or money), sure, Python 2.7 support will continue. I just hope those same people have used the past years to do calculate the cost of moving to Python 3 vs the cost of Python 2 support. Expecting Python 2 support to be free or even easy is delusional/selfish though.

Pffft. Nice strawman. Who said it would be free or easy?

Expecting that everyone will just hop over Python 3 because one group of people doesn't want to maintain Python 2 anymore is delusional.

Re: Python 2.7 Countdown

#30

Post by yeukhon »

alergico wrote: post #10

Guess the community (or a company like RedHat) will have to step in and fork 2.7. There is no way that people who haven't switched, will want to switch, unless absolutely forced to (for example: no security patches).

Has RedHat ever forked Python from 2.3 all the way to 2.6?
Post reply on HN