4 ms·

The difference is that Python 3 is far more backwards incompatible than an update to Ruby, Go or Java. If there's any component of your Python project that was

The difference is that Python 3 is far more backwards incompatible than an update to Ruby, Go or Java. If there's any component of your Python project that was written for Python 2 and it hasn't been ported, your project as a whole is probably staying in Python 2. I certainly wouldn't call the Python 3 path "dead", as starting a new project you'd be silly not to use Python 3. It's just a very slow process. Also, porting from 2 to 3 isn't even that hard (there's a script that does 95% of it for you).

sandGorgon 11y ago
I understand this in its abstract sense - but I think (IMHO) the fundamental problem is that every framework out there is using Python 2.7.... which means nobody is using it. I'm not sure if you have worked in the Ruby or Go ecosystem... but if you are starting a new project, you are using latest Ruby+latest Rails. this is not the case in Python. I asked a question here and on the /r/python forums. What framework should one use to build an API using asyncio+postgresql. Nobody seems to be doing it. the answers I got mentioned using Tornado with Python 3 code on top of it. People have compared asyncio with goroutines - but even for a project that is a migration from Go -> Python by a fairly advanced developer ... Py 2.7 is being used.
- Too 11y ago
  > every framework out there is using Python 2.7.... That's just FUD, it might have been true many years ago but not any longer. http://python3wos.appspot.com/ http://python3wos.appspot.com/, there are a few red holes but from what I could tell some of those have substitutes that in many cases are better even. It might also be true for in house libraries but at least there you have the chance to upgrade yourself.
  - sandGorgon 11y ago
    I know that. But I'm hard pressed to find anyone who is using this stuff in production. the ecosystem is still running 2.7. I cant wait to switch to Py3.
    - azazel75 11y ago
      > the ecosystem is still running 2.7. I cant wait to switch to Py3. Which one? Pyramid and SQLAlchemy work like a charm in Py3. Until you really name what your need is, that's just fud.

sandGorgon 11y ago

I understand this in its abstract sense - but I think (IMHO) the fundamental problem is that every framework out there is using Python 2.7.... which means nobody is using it. I'm not sure if you have worked in the Ruby or Go ecosystem... but if you are starting a new project, you are using latest Ruby+latest Rails. this is not the case in Python. I asked a question here and on the /r/python forums. What framework should one use to build an API using asyncio+postgresql. Nobody seems to be doing it. the answers I got mentioned using Tornado with Python 3 code on top of it. People have compared asyncio with goroutines - but even for a project that is a migration from Go -> Python by a fairly advanced developer ... Py 2.7 is being used.

Too 11y ago
> every framework out there is using Python 2.7.... That's just FUD, it might have been true many years ago but not any longer. http://python3wos.appspot.com/ http://python3wos.appspot.com/, there are a few red holes but from what I could tell some of those have substitutes that in many cases are better even. It might also be true for in house libraries but at least there you have the chance to upgrade yourself.
- sandGorgon 11y ago
  I know that. But I'm hard pressed to find anyone who is using this stuff in production. the ecosystem is still running 2.7. I cant wait to switch to Py3.
  - azazel75 11y ago
    > the ecosystem is still running 2.7. I cant wait to switch to Py3. Which one? Pyramid and SQLAlchemy work like a charm in Py3. Until you really name what your need is, that's just fud.