5 ms·

I wished this Python 2 and Python 3 was done with more carrot and whip to move people over to 3. It has been over a decade and we still have divided community.

infogulch 9y ago
It's gained much more momentum over just the last year from what I can see.
sametmax 9y ago
The community is not divided anymore. Anybody who knows wants to use 3. Anybody who doesn't is told to. The only people using Python 2 are now people stuck with legacy code base. It's an important part, but the situation is very clear.
- user5994461 9y ago
  The situation is very clear, any code base that is older than 5 years and more than a million lines will be forever stuck with python 2.
- sandGorgon 9y ago
  > The only people using Python 2 are now people stuck with legacy code base Like tensorflow - https://github.com/tensorflow/tensorflow/issues/1 https://github.com/tensorflow/tensorflow/issues/1
  - chronial 9y ago
    You do realize that that issue was closed in 2015, right?
  - IanOzsvald 9y ago
    tensorflow looks to work fine with Python 3.4+ https://github.com/tensorflow/tensorflow https://github.com/tensorflow/tensorflow I've just installed it using conda in Python 3.6 just fine.
- coldtea 9y ago
  >The only people using Python 2 are now people stuck with legacy code base. So, just largest and more important part of Python's non-hobbyist users?
maxerickson 9y ago
Python 3.0 was released December 3rd, 2008, 8.5 years ago. I don't really remember all that clearly, but my recollection is that numerous caveats were made fairly clear (like the new IO not being optimized and so on). I guess something needed to go out the door but I wonder if the biggest mistake was calling that release the 3.0 release (rather than something that would have better tempered naive expectations).
- eat_veggies 9y ago
  The changes were breaking enough that a 2.x release wouldn't have been appropriate, so I get why they did that.
  - maxerickson 9y ago
    I mean something like branding the initial release as a "Python 3 Developer Preview" or something. A line in the sand where the goal is release quality but with less implication that it is now the preferred version (because there was a big ecosystem of libraries to move over and such)
jxramos 9y ago
I take it on a project by project basis. We have a bunch of legacy 2.x stuff running at work but when I began to greenfield new projects I made them 3.0 from the start. Folks at work asked why I made our codebase mixed with Python versions and I answered because I'm creating isolated tool projects from scratch and have no real constraints to use Python 2. It's made some issues for folks having to install both versions of python but it's been a pretty minor issue thus far.
amenod 9y ago
This. I don't care if I'm using Python 2 or 3, but I really hate switching between two similar, but not completely equal, languages. The rift made Python more damage than a forceful switch would, IMHO of course.

infogulch 9y ago

It's gained much more momentum over just the last year from what I can see.

sametmax 9y ago

The community is not divided anymore. Anybody who knows wants to use 3. Anybody who doesn't is told to. The only people using Python 2 are now people stuck with legacy code base. It's an important part, but the situation is very clear.

user5994461 9y ago
The situation is very clear, any code base that is older than 5 years and more than a million lines will be forever stuck with python 2.
sandGorgon 9y ago
> The only people using Python 2 are now people stuck with legacy code base Like tensorflow - https://github.com/tensorflow/tensorflow/issues/1 https://github.com/tensorflow/tensorflow/issues/1
- chronial 9y ago
  You do realize that that issue was closed in 2015, right?
- IanOzsvald 9y ago
  tensorflow looks to work fine with Python 3.4+ https://github.com/tensorflow/tensorflow https://github.com/tensorflow/tensorflow I've just installed it using conda in Python 3.6 just fine.
coldtea 9y ago
>The only people using Python 2 are now people stuck with legacy code base. So, just largest and more important part of Python's non-hobbyist users?

maxerickson 9y ago

Python 3.0 was released December 3rd, 2008, 8.5 years ago. I don't really remember all that clearly, but my recollection is that numerous caveats were made fairly clear (like the new IO not being optimized and so on). I guess something needed to go out the door but I wonder if the biggest mistake was calling that release the 3.0 release (rather than something that would have better tempered naive expectations).

eat_veggies 9y ago
The changes were breaking enough that a 2.x release wouldn't have been appropriate, so I get why they did that.
- maxerickson 9y ago
  I mean something like branding the initial release as a "Python 3 Developer Preview" or something. A line in the sand where the goal is release quality but with less implication that it is now the preferred version (because there was a big ecosystem of libraries to move over and such)

jxramos 9y ago

I take it on a project by project basis. We have a bunch of legacy 2.x stuff running at work but when I began to greenfield new projects I made them 3.0 from the start. Folks at work asked why I made our codebase mixed with Python versions and I answered because I'm creating isolated tool projects from scratch and have no real constraints to use Python 2. It's made some issues for folks having to install both versions of python but it's been a pretty minor issue thus far.

amenod 9y ago

This. I don't care if I'm using Python 2 or 3, but I really hate switching between two similar, but not completely equal, languages. The rift made Python more damage than a forceful switch would, IMHO of course.