News for hackers. Stuff that matters.
Re:Where are we in the Python 3 transition? by hoodoof on Friday January 01, 2016 @06:28PM (#10824075)
>> huge number of users that will never switch to Python 3

I don't believe this assertion.

All companies, projects, and developers have to move to the current version of Python eventually. Python 2 eventually is no longer supported. Python libraries will start to drop support for Python 2. Developers will see that for their career they need to have Python 3 skills. Jobs ads will require Python 3. Linux distros will drop Python 2. New libraries will start to appear that are only Python 3.

Don't know when, but Python 2 will suddenly look very old.

Re:Where are we in the Python 3 transition? by kec on Friday January 01, 2016 @07:19PM (#10824293)
Given that there are significant differences between python2 and 3, such that porting large codebases is a nontrivial task, why do you assume people with automatically decide to proceed with python3 instead of some other language? At this point, python3 doesn't just have to be better than python2, it also has to be better than Clojure/Swift/Julia/C++14/name a modern language.
Re:Where are we in the Python 3 transition? by hoodoof on Friday January 01, 2016 @07:42PM (#10824359)
>> Given that there are significant differences between python2 and 3

Really? I don't think they are that different. If it was so different and hard to port then why have so many libraries been successfully update to support both http://py3readiness.org/

You can't generalise but for the most part updating from Python 2 to Python 3 is likely to be easier and less risky and costly than doing a full rewrite in some other language.

Some companies might rebuild in another language, that happens all the time - things get rebuilt from this to that.

But why would a company ditch Python entirely in such a situation?

Re:Where are we in the Python 3 transition? by dozzie on Friday January 01, 2016 @07:10PM (#10824258)
> All companies, projects, and developers have to move to the current version of Python eventually.

Well, yes, and that "eventually" is somewhere in ten or fifteen years.

Re:Where are we in the Python 3 transition? by hoodoof on Friday January 01, 2016 @07:36PM (#10824340)
There's no way to know the timeframe but tipping points can come very suddenly.

I've seen a number of companies get stuck with a large code base built on old technology and it causes them huge problems, chiefly around finding people who can (and are willing to) program with an obsolete language. Companies with large Python 2 code bases will make things easier for themselves if they start making the transition sooner rather than later.