3 ms·
I see a lot of comments about Python 3 was 12 years ago. Yes. But Python 3.0 - 3.4 were not usable. Most important third-party libraries were only ported Pytho
by satya71 6y ago
I see a lot of comments about Python 3 was 12 years ago. Yes. But Python 3.0 - 3.4 were not usable.
Most important third-party libraries were only ported Python 3.5 onward. So the real Python 3 start date should be 2015, not 2008.
- mixmastamyk 6y agoThe tools for upgrading code to Py3 paradigms started in 2.6 however. There was plenty of time to do it. Unless a project dealt heavily with unicode the transition was trivial if any effort was made.
- satya71 6y agoYes the translation tools existed, but they were not quite enough. Besides real world doesn't move in one swoop. You need co-existence. I very much wanted to move to Python 3, but critical libraries I was using were not there. And running both 2 and 3 at the same time was very unergonomic until python-future [1] became stable and widely-used. [1] http://python-future.org/ http://python-future.org/
- mixmastamyk 6y agoA decade is pretty good for free support. You are welcome to pay to continue as well. About five years ago I used six and it worked well enough. Now both obsolete.
- heavyset_go 6y agoI started a couple of green field projects in Python 3.3 and Python 3.4, and have to disagree. By that time most third party packages had moved to Python 3, and I had no trouble building large applications with it.