Live data from Hacker News

PyPy 2.0 Released

morepypy.blogspot.com

11–20 of 77 posts

Re: PyPy 2.0 Released

#11
post #3

Can someone knowledgeable compare PyPy, Numba and Cython? I mostly use Cython. Tried Numba also, it has very nice workflow when it works with autojit (when it doesn't error messages are pretty cryptic). With PyPy I don't understand why for example all that type information obtained from jit wouldn't be used to make something like Numba specialized functions or Cython modules (noob question but please answer).

PyPy still doesn't work with Numpy, though they're working on it.

Re: PyPy 2.0 Released

#13
post #9
post #8

Earlier quoted context omitted.

For example does PyPy always warm up, or can it store "warmed up" version of some function (where type of objects is inferred)? I know that this is not in accordance with highly dynamic nature of Python, but not all functions are highly dynamic.

Do you mean can you save the state of the JIT for future use?

Yeah. Can you? Considering CPython already generates .pyc and checks timestamps, keeping some kind of JIT cache around wouldn't be a stretch.

Re: PyPy 2.0 Released

#15
post #9

Earlier quoted context omitted.

Do you mean can you save the state of the JIT for future use?

Yeah. Can you? Considering CPython already generates .pyc and checks timestamps, keeping some kind of JIT cache around wouldn't be a stretch.

No, the state of the JIT cannot be saved between executions.

Re: PyPy 2.0 Released

#16
post #4

Congratulations! Looking forward to the day PyPy becomes the reference implementation.

I hope that that never happens. CPython is still pretty readable, and reference implementations should be simple and easy to learn from.

Actually, I'd like it if somebody hacked up a very very simple and naive Python interpreter and nominated that for the reference implementation instead.

Re: PyPy 2.0 Released

#17
post #11
post #3

Can someone knowledgeable compare PyPy, Numba and Cython? I mostly use Cython. Tried Numba also, it has very nice workflow when it works with autojit (when it doesn't error messages are pretty cryptic). With PyPy I don't understand why for example all that type information obtained from jit wouldn't be used to make something like Numba specialized functions or Cython modules (noob question but please answer).

PyPy still doesn't work with Numpy, though they're working on it.

Numba is not Numpy.

Re: PyPy 2.0 Released

#18
post #4

Congratulations! Looking forward to the day PyPy becomes the reference implementation.

The Python Foundation should really give some money/developers to these guys

Re: PyPy 2.0 Released

#20
post #11
post #3

Can someone knowledgeable compare PyPy, Numba and Cython? I mostly use Cython. Tried Numba also, it has very nice workflow when it works with autojit (when it doesn't error messages are pretty cryptic). With PyPy I don't understand why for example all that type information obtained from jit wouldn't be used to make something like Numba specialized functions or Cython modules (noob question but please answer).

PyPy still doesn't work with Numpy, though they're working on it.

That's not quite right. Stock numpy doesn't install, and nobody's working on that as far as I know, but they've reimplemented part of the numpy API (at least the Python API, not the C one), and the subset they've implemented works fine. I have an application in production that uses it.
Post reply on HN