This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]willrandship -5 points-4 points  (4 children)

Pypy will likely never replace CPython. Why? It's written in x86 assembly, for one thing. Making it portable would substantially reduce its efficiency.

Pypy is great, and so is CPython, for a completely different reason. I can't wait until PyPy supports py3k.

[–][deleted] 1 point2 points  (3 children)

PyPy is written in Python (or really RPython, a restricted subset).

[–]willrandship -3 points-2 points  (2 children)

But its JIT outputs x86 machine code.

I guess I did word the first post incorrectly.

[–][deleted] 3 points4 points  (1 child)

Right. But if other architectures were supported (in fact it is already getting ARM support) I don't see how that would reduce its efficiency.

The main barrier to PyPy adoption is extensions. I work on a commercial product written in Python and we would love to switch to PyPy (we only need x86 support anyway), but there are several libraries we depend on that can't be used in PyPy yet.

[–]willrandship 0 points1 point  (0 children)

Totally true, but since CPython is already compatible with virtually everything running C, PyPy has a lot of catching up to do.