for me the bigger issue is that while it's +1 to speed, it's -5 to memory.
Re:Navigating the Postmodern Python World
by MostAwesomeDude on Thursday July 11, 2013 @02:27PM
(#6028076)
It is not up to PyPy to support non-pure-Python libraries; it is up to those libraries to fix themselves by evicting their C and FORTRAN balls and chains.
It might not be PyPy's fault, but it is PyPy's problem.
If I have code that wants those libraries, PyPy is not an option. As an end user, I don't care who should fix it. I just know that I can't get my job done with PyPy.
The Zen of Python states that "practicality beats purity."
And the authors of numpy, scipy, pandas, etc seem to agree that it would be impractical to rewrite these libraries in the way you are suggesting.
Re:Navigating the Postmodern Python World
by MostAwesomeDude on Thursday July 11, 2013 @11:07PM
(#6030682)
"Special cases aren't special enough to break the rules."
Absolutely. But that's somewhat tangential to the question of whether or not Python is fast AND has good libraries. Regardless of blame, it doesn't change the fact that Python doesn't meet that criteria.
You can't say that Python has both speed and great libraries. It has one or the other. Hopefully this will change at some point and I'll be able to reap the benefits of both.