3 ms·

The other way of looking at it is that 2.7 is EOL in 2020, and there will be no further 2.x. 2.x is very much a dead end. http://legacy.python.org/dev/peps/pep

by fnj 10y ago

The other way of looking at it is that 2.7 is EOL in 2020, and there will be no further 2.x. 2.x is very much a dead end. http://legacy.python.org/dev/peps/pep-0373/ http://legacy.python.org/dev/peps/pep-0373/

afarrell 10y ago
Like COBOL
BuuQu9hu 10y ago
The PyPy team will support Python 2 indefinitely: https://morepypy.blogspot.com/2016/08/pypy-gets-funding-from-mozilla-for.html https://morepypy.blogspot.com/2016/08/pypy-gets-funding-from... We never have to leave Python 2, if we do not want to.
- no_wizard 10y ago
  This comes up over and over again in the Python community. If you will allow me to paint with broad strokes, as I'm going to lump a lot of things together for the sake of ease of understanding, I am not speaking for every python user(s) out there. There seems to be a huge tug of war between companies/corporate users and the PSF & more independent users. The smaller (if you will, these are going to be big in the python community) 'shops' and library developers, and users all are or have migrated to Python 3 ages ago. Django now is going to be python 3 only in the foreseeable future (I know they EOL'd their python2 compatible libraries). The Software foundation itself wants it to be essentially toast by 2020. Things like Pyramid, Flask, Bottle, and even numpy & scipy have started moving in a direction of having python3 be their 'first' update (I think in the case of Flask and Bottle, they're end of life support for python2 is happening as well, though they haven't announced anything official, they seem to be adding new features and promising features that will only make sense in python3). Yet, big 'corporate' users like Google (Look at you, grumpy https://github.com/google/grumpy https://github.com/google/grumpy) and Apple (still shipping with 2.7...and why!) and large universities all seem to be stuck on python 2. Because of this, this to me really hurts the community and its holding back full development of python3 and python generally going forward. Why are companies holding back the state of a language (and then complaining about it) instead of diverting their ya know, massive resources, to get their own libraries and technologies up to current stack? Why do so many people want to stay on python2. I'll never understand. For what its worth, the latest version of python3 (3.6, well, 3.6.1, but the release notes for this is for 3.6) haves a ton of forward thinking built in concurrency improvements and technologies that these companies could easily take advantage of! https://docs.python.org/3/library/concurrency.html https://docs.python.org/3/library/concurrency.html https://docs.python.org/3/library/asyncio.html https://docs.python.org/3/library/asyncio.html https://docs.python.org/3/library/multiprocessing.html https://docs.python.org/3/library/multiprocessing.html
  - jjawssd 10y ago
    Lack of ROI (return on investment) is why people stay on Python 2
    - no_wizard 10y ago
      Then why hold everyone else back if you aren't willing to push forward? At least with new projects it'd be great if people used Python 3. Google's choice with Grumpy particularly astounds me. Why 2.7? Its not clear to me and in fact, its really unclear to me, why that was a 'better' choice.
      - dragonwriter 10y ago
        > Google's choice with Grumpy particularly astounds me. Why 2.7? Probably because Google has a lot of legact Python 2.7, and doesn't do new greenfield development in Python 3, preferring other languages (particularly Go), so... Projects made to scratch the maker's own itch are good in that they get thoroughly dogfooded, but they also can carry a focus that reflects the creator's needs more than anyone else's.
      - takeda 10y ago
        Grumpy looks to me like it was created as a bridge to port everything to Go. If you look at it from that perspective and know that Google has a lot of existing python 2 code base, it makes a lot of sense. If they wanted to stick with python, instead of grumpy, they would instead provide a way to write python modules in go.

by fnj 10y ago

afarrell 10y ago

Like COBOL

BuuQu9hu 10y ago

The PyPy team will support Python 2 indefinitely: https://morepypy.blogspot.com/2016/08/pypy-gets-funding-from-mozilla-for.html https://morepypy.blogspot.com/2016/08/pypy-gets-funding-from... We never have to leave Python 2, if we do not want to.

no_wizard 10y ago
This comes up over and over again in the Python community. If you will allow me to paint with broad strokes, as I'm going to lump a lot of things together for the sake of ease of understanding, I am not speaking for every python user(s) out there. There seems to be a huge tug of war between companies/corporate users and the PSF & more independent users. The smaller (if you will, these are going to be big in the python community) 'shops' and library developers, and users all are or have migrated to Python 3 ages ago. Django now is going to be python 3 only in the foreseeable future (I know they EOL'd their python2 compatible libraries). The Software foundation itself wants it to be essentially toast by 2020. Things like Pyramid, Flask, Bottle, and even numpy & scipy have started moving in a direction of having python3 be their 'first' update (I think in the case of Flask and Bottle, they're end of life support for python2 is happening as well, though they haven't announced anything official, they seem to be adding new features and promising features that will only make sense in python3). Yet, big 'corporate' users like Google (Look at you, grumpy https://github.com/google/grumpy https://github.com/google/grumpy) and Apple (still shipping with 2.7...and why!) and large universities all seem to be stuck on python 2. Because of this, this to me really hurts the community and its holding back full development of python3 and python generally going forward. Why are companies holding back the state of a language (and then complaining about it) instead of diverting their ya know, massive resources, to get their own libraries and technologies up to current stack? Why do so many people want to stay on python2. I'll never understand. For what its worth, the latest version of python3 (3.6, well, 3.6.1, but the release notes for this is for 3.6) haves a ton of forward thinking built in concurrency improvements and technologies that these companies could easily take advantage of! https://docs.python.org/3/library/concurrency.html https://docs.python.org/3/library/concurrency.html https://docs.python.org/3/library/asyncio.html https://docs.python.org/3/library/asyncio.html https://docs.python.org/3/library/multiprocessing.html https://docs.python.org/3/library/multiprocessing.html
- jjawssd 10y ago
  Lack of ROI (return on investment) is why people stay on Python 2
  - no_wizard 10y ago
    Then why hold everyone else back if you aren't willing to push forward? At least with new projects it'd be great if people used Python 3. Google's choice with Grumpy particularly astounds me. Why 2.7? Its not clear to me and in fact, its really unclear to me, why that was a 'better' choice.
    - dragonwriter 10y ago
      > Google's choice with Grumpy particularly astounds me. Why 2.7? Probably because Google has a lot of legact Python 2.7, and doesn't do new greenfield development in Python 3, preferring other languages (particularly Go), so... Projects made to scratch the maker's own itch are good in that they get thoroughly dogfooded, but they also can carry a focus that reflects the creator's needs more than anyone else's.
    - takeda 10y ago
      Grumpy looks to me like it was created as a bridge to port everything to Go. If you look at it from that perspective and know that Google has a lot of existing python 2 code base, it makes a lot of sense. If they wanted to stick with python, instead of grumpy, they would instead provide a way to write python modules in go.