MacOS still ships with Python 2 as the default python.
Macos still ships an outdated openssl, bash, etc etc... Apple are the definition of “lag” for developer tools.
Python 2.7 Countdown
11–20 of 72 posts
Re: Python 2.7 Countdown
#12MacOS 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]
Re: Python 2.7 Countdown
#13Re: Python 2.7 Countdown
#14Is Python 3 an officially supported language at Google yet?
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 service which runs almost whatever you want.
People really shouldn’t try to position flexible as a new version of GAE. It’s a totally different service. If everyone who’s currently using standard had to switch to flexible, Many if their bills would go up. Is Google EOLing standard?
Re: Python 2.7 Countdown
#15MacOS 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)
Re: Python 2.7 Countdown
#16Guess 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.
Re: Python 2.7 Countdown
#17If there is Python 4, please, make it backwards compatible. Thank you.
Re: Python 2.7 Countdown
#18Guess 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.
Re: Python 2.7 Countdown
#19If there is Python 4, please, make it backwards compatible. Thank you.
A major version bump does tend to imply breaking changes.
Re: Python 2.7 Countdown
#20MacOS still ships with Python 2 as the default python.
Macos still ships an outdated openssl, bash, etc etc... Apple are the definition of “lag” for developer tools.
It has to do with licenses. They're shipping the last GPLv2 version of bash for one, the new versions are on GPLv3.
I don't get why people bash things when they clearly don't understand the full context (pun intended ;)