Couldn't agree more, I maintain multiple scientific software packages with a combined total of ~20k lines. Last week we decided to make the jump from 2 to 3. Within about a day we managed to port two of our projects with backwards compatibility. The third party libraries are there, 2to3 ported something like 80% of codebase correctly and the rest was trivial to fix. I feel for people who are stuck with large Python 2 codebases but if your employer can't, over the span of 5 years, devote some man-hours to make your system future proof, then blame them not Guido or the volunteers who have made the wonder that is Python in the first place.
What python3 strategy? python3 is just as slow as python2. And pypy is a very nice idea, but it also requires porting and rewriting every library that's written in c and also has that annoyin GIL... Don't get me wrong, I really like python, just not for technical computing.
Anyway, my point was that Julia is being pragmatic and realises if they will convert python people they should have an interop story so codebases and be converted piecewise. PyPy basically says "C is lame, we will be faster, who uses numpy anyway" which is, lets say, a bold claim. Python3 patronizes us solid Py2 uses and made backwards incompatible changes such that you had to switch your stack over more or less at once.
I am a big fan of incremental optimization, incremental porting, and incremental interop.
Now, I really like python and use it for technical computing excessively. It is fast enough because the developer time I save building the entire stack I can, after profiling obviously, use to optimize (using any one of the many python strategies available) only the hot parts of the code. With all my remaining spare time I can bitch on reddit about how Python is slow.
PyPy basically says "C is lame, we will be faster, who uses numpy anyway" which is, lets say, a bold claim.
That's not true, PyPy is just incompatible/slow with the C extension API, if the C API was more implementation independent, PyPy would be fine with it.
57
u/Phild3v1ll3 May 27 '14
Couldn't agree more, I maintain multiple scientific software packages with a combined total of ~20k lines. Last week we decided to make the jump from 2 to 3. Within about a day we managed to port two of our projects with backwards compatibility. The third party libraries are there, 2to3 ported something like 80% of codebase correctly and the rest was trivial to fix. I feel for people who are stuck with large Python 2 codebases but if your employer can't, over the span of 5 years, devote some man-hours to make your system future proof, then blame them not Guido or the volunteers who have made the wonder that is Python in the first place.