News for hackers. Stuff that matters.
Re:Python 3 in Science: the great migration has begun by coldtea on Saturday May 09, 2015 @09:06PM (#9518314)
>But this is all wrong – we should be teaching new users to use Python 3! New users won't thank you if you teach them Python 2 and they have to migrate all their scripts to Python 3 in a few years...

Believe me, they won't have to. Python 2 will stay with us for a loooong time, and most NEW web stuff AND scientific work is done with it.

>However, the Python developers have now stated that there will be no Python 2.8 release. Essentially, no new features are going to be added to Python 2. In fact, after 2020 (which is not so far in the future), Python 2 will no longer be supported.

Yeah, let's see how this works out. After all it's the same guys who said that Python 3 transition would end with 3 being the default choice by 2014.

Re:Python 3 in Science: the great migration has begun by coliveira on Saturday May 09, 2015 @10:46PM (#9518588)
Whatever the result of this, the transition Python 2->3 will remain as one of the most troubled ever for a mainstream programming language (of course, nothing beats Perl 5 on this area). If you consider that Java is on version 8 and C++14 is here, we can see that even old languages have done this in a much more organized way.
Re:Python 3 in Science: the great migration has begun by lqdc13 on Saturday May 09, 2015 @11:52PM (#9518724)
Isn't Python the only one with breaking changes out of this group?
Re:Python 3 in Science: the great migration has begun by unscaled on Sunday May 10, 2015 @01:58AM (#9519015)
Which group are you referring to? Mainstream languages? The languages mentioned above? Perl 6 was designed from start to be very breaking, but even putting Perl 6 aside, Ruby had quite a few breaking changes going from 1.8 to 1.9 - and that was a merely point release.

Breaking changes are tough, but many libraries with a large codebase managed to update to Python 3 and even maintain dual-version support using compatible features, compatibility libraries and automated conversion tools.

For the everyday users things would be much simpler, and hence the main reasons for converting is not "too many breaking changes" but rather "not enough compelling changes".

Re:Python 3 in Science: the great migration has begun by maxerickson on Sunday May 10, 2015 @08:33AM (#9519712)
It's probably reasonable to compare the breaking changes in Ruby 1.9 to Python 1.6/2.0, when Python first added language support for Unicode. There wasn't much in the way of blow back.

If there is at some point a decision to significantly change the semantics of string handling in Ruby (I think tagged strings are the addition of string handling, not a change to it), expect just as much whining as Python has seen (but I think people will look at how it has gone and avoid doing it).

Re:Python 3 in Science: the great migration has begun by lqdc13 on Sunday May 10, 2015 @08:24AM (#9519698)
I was replying to

"If you consider that Java is on version 8 and C++14 is here, we can see that even old languages have done this in a much more organized way"

C++14 and Java have extremely minor breaking changes.

I'm not saying it has to be that way, but the demographic that uses Ruby is different from the demographic that uses those other languages and Python.

But the main thing is probably that Python 2 is the default version on OSX and Ubuntu.

Updating to a newer version requires going to the Python site or installing Brew/Macports.