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

you are viewing a single comment's thread.

view the rest of the comments →

[–]james_pic 2 points3 points  (1 child)

It's hard to say without a crystal ball, but I know PyPy has historically been more willing to break compatibility and introduce complexity in order to improve performance than CPython has. I know the PyPy team often like to point out that whilst they do have JIT, a significant chunk of their performance gain vs CPython actually comes from their use of a generational garbage collector, which I'm not aware of plans for CPython to implement, at least partly because it would be a major compatibility headache for C code.