3 ms·

It's insane to think that Python 2 is going to go away because of the existence of Python 3. That is simply not how computer languages work. Python 2 has more t

It's insane to think that Python 2 is going to go away because of the existence of Python 3. That is simply not how computer languages work. Python 2 has more than enough critical mass to continue pretty much forever in some form. It is even a reasonable target for new development because it is pretty much guaranteed to be stable. I would not be surprised if there was another initiative to fix Python 2's Unicode handling that would create a fork from Python 3 in the future as Python 3 took an approach that did not catch on.

newen 9y ago
So true. Just last week I thought I would start to use python 3 because I was starting on a new project and had a new computer. I installed anaconda python 3 only to have it crash when starting jupyter because the new python 3 version doesn't support backtick quoting for some reason, and jupyter was using backtick quoting. Oh well, back to python 2 for me, which will be stable for at least 2 years. Hopefully by then, I will be able to switch to another language.
- sametmax 9y ago
  Jupyter doesn't use backstick quoting if you install it from Python 3.
Fnoord 9y ago
> That is simply not how computer languages work. True, not how major revisions work, indeed. Elephant in the room is that this is a chicken/egg problem. The best of both worlds is a temporary transition period where you can run both (like we want both IPv4 native and IPv6 native). Unfortunately because that doesn't get adopted either we get in a situation where people need to pick either. Articles like these help, but I use Chocolatey to maintain software on a Windows system.
sametmax 9y ago
> Python 3 took an approach that did not catch on. In your world maybe, but 97% of the project and training I took part where python 3 since Python 3.5 came out. And this spans in a lot of companies and countries.

newen 9y ago

So true. Just last week I thought I would start to use python 3 because I was starting on a new project and had a new computer. I installed anaconda python 3 only to have it crash when starting jupyter because the new python 3 version doesn't support backtick quoting for some reason, and jupyter was using backtick quoting. Oh well, back to python 2 for me, which will be stable for at least 2 years. Hopefully by then, I will be able to switch to another language.

sametmax 9y ago
Jupyter doesn't use backstick quoting if you install it from Python 3.

Fnoord 9y ago

> That is simply not how computer languages work. True, not how major revisions work, indeed. Elephant in the room is that this is a chicken/egg problem. The best of both worlds is a temporary transition period where you can run both (like we want both IPv4 native and IPv6 native). Unfortunately because that doesn't get adopted either we get in a situation where people need to pick either. Articles like these help, but I use Chocolatey to maintain software on a Windows system.

sametmax 9y ago

> Python 3 took an approach that did not catch on. In your world maybe, but 97% of the project and training I took part where python 3 since Python 3.5 came out. And this spans in a lot of companies and countries.