Pyjion VS pypy

Looks like it was started at Microsoft, the tonybaloney/Pyjion was forked from microsoft/Pyjion.

Pyjion is a Microsoft project that adds a JIT leveraging CoreCLR.

https://github.com/microsoft/Pyjion was a really nice attempt to marry CPython with JIT in a rather generic way, but it was abandoned quickly.

There are articles like https://instagram-engineering.com/dismissing-python-garbage-... which seem to confirm some problems. One of the people involved with this Cinder project was an original author of https://github.com/microsoft/Pyjion (it's now being revamped by a new dev.) Dino had deep .NET/CLR implementation experience and had been the lead for IronPython which I think spawned the interest in perf improvements through Cinder. I hope this effort is more successful for him.

You'll note I said I was playing with RPython, not PyPy. In my case, I was playing with writing a small interpreter, and comparing the RPython toolchain with the Truffle/Graal framework.

Writing RPython code, even if one is not developing or contributing to PyPy, means writing within a subset of python 2.

> RPython ("Restricted Python") is a subset of Python 2

https://www.pypy.org/posts/2022/04/how-is-pypy-tested.html

And RPython's translator specifically uses pypy, and uses python 2 syntax:

https://github.com/pypy/pypy/blob/main/rpython/bin/rpython#L...

... so getting the RPython toolchain (even if one is intending to improve the PyPy 3+ interpreters) requires setting up a pypy 2 interpreter. Hence the question in my post.