What advantages does this provide beyond what can be achieved with Cython?
People are in love with the idea of a Pythonic language with the speed of an ahead of time compiled language. The issue is without 100% compatibility with existing CPython code, enabling you to use the existing interesting libraries of the Python ecosystem, you’ll get no interest.
There is a trivial subset of python which seems it could be made substantially faster, for example integer / floating point operations. Frustratingly people make attempts and get nowhere, encountering resistance and red tape. (See
https://discuss.python.org/t/using-tagged-pointers-to-suppor...).
We even had this project, Pon, posted about 3 months ago (https://github.com/can1357/pon).
> pon is a JIT & AoT native compiler and runtime for Python 3.14, written in Rust.
This is all anyone has ever wanted. It was basically dismissed, and hasn’t been worked on since it was posted. If a project like that can’t inspire interest, I don’t know what will.
People are in love with the idea of a Pythonic language with the speed of an ahead of time compiled language. The issue is without 100% compatibility with existing CPython code, enabling you to use the existing interesting libraries of the Python ecosystem, you’ll get no interest.
There is a trivial subset of python which seems it could be made substantially faster, for example integer / floating point operations. Frustratingly people make attempts and get nowhere, encountering resistance and red tape. (See https://discuss.python.org/t/using-tagged-pointers-to-suppor...).
We even had this project, Pon, posted about 3 months ago (https://github.com/can1357/pon).
> pon is a JIT & AoT native compiler and runtime for Python 3.14, written in Rust.
This is all anyone has ever wanted. It was basically dismissed, and hasn’t been worked on since it was posted. If a project like that can’t inspire interest, I don’t know what will.