News for hackers. Stuff that matters.
Re:PyPy2.7 and PyPy3.5 v5.7 released by fijal on Tuesday March 21, 2017 @01:07PM (#13924118)
numpy works, scipy & matplotlib are very close. Stop spreading false information please.

That said, the cpython+cython solution is not going away any time soon.

Re:PyPy2.7 and PyPy3.5 v5.7 released by hyperbovine on Tuesday March 21, 2017 @03:27PM (#13925366)
> numpy works, scipy & matplotlib are very close.

Care to elaborate? I agree that numpypy is pretty much complete, though I have not found it to be faster in my limited testing. I was under the impression that a great deal of work would be required to get the other two running, even using CPyExt (which would not be faster, which was the whole point to begin with). I'd love to be proved wrong though.

Re:PyPy2.7 and PyPy3.5 v5.7 released by mattip on Tuesday March 21, 2017 @04:12PM (#13925773)
Real world use cases are large and messy. Now that the cython/pandas/numpy stack works out of the box on PyPy, we can begin to see how often the mix of python code (jittable, fast) and c code (fast) needs to cross the c-to-python barrier (slow). There may be some cases, like NLP where speeding up parsing and io can make a difference
Re:PyPy2.7 and PyPy3.5 v5.7 released by fijal on Wednesday March 22, 2017 @04:06AM (#13929206)
numpy, pandas (mostly) and (scipy) mostly work through cpyext. We're considering how to make them fast now. It would never be faster on large_array + large_array, but it should be faster (by a lot) with element access etc., bit like numba