Pyjion

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.

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.

I find it really interesting, that not only did they do the work of creating a JIT using the CoreCLR for CPython, they created a JIT API so that their system is augmenting CPython and not taking it over. Solid engineering. This also means that one could implement an alternative JIT using Rust or OCaml. https://github.com/microsoft/Pyjion#what-are-the-goals-of-th...

On the repo there's also a comparison[1] with some of the other implementations. [1]: https://github.com/microsoft/Pyjion#how-do-this-compare-to-

One more: https://github.com/microsoft/Pyjion

Related (though seems abandoned:) https://github.com/microsoft/Pyjion

There’s a project to plug different JIT compilers into CPython, so there’s hope. https://github.com/Microsoft/Pyjion/blob/master/README.md Also, I’ve more than once seen cpython beat C++/Fortran since it’s easier to do the right algo/datastructure things, plus numpy is more optimized than most «amateur» C loop-over-arrays. That being said, faster python is always welcome.

Related: https://github.com/Microsoft/Pyjion

We [msft python team] tried to get PyPy some funding, but it didn't go very far. I'll keep trying. We've also started this project to enable jitting for CPython: https://github.com/Microsoft/Pyjion The core of it is there and it's been accepted into the main trunk, but we haven't had the cycles to do quality codegen yet.

Have a look at this: https://github.com/Microsoft/Pyjion

there are several. we (microsoft) are also trying to get an api into cpython so that anyone can use to build JITs for python. our sample implementation is at: https://github.com/Microsoft/Pyjion pycon 2016 talk: https://www.youtube.com/watch?v=1DAIzO3QXcA

Similar effort by Microsoft: https://github.com/Microsoft/Pyjion

there's also Microsoft's effort: https://github.com/Microsoft/Pyjion [disclaimer]

With Pyjion on the way from MS and the Python core devs declaring if it works they'll make the API changes[0] to connect CPython3 to an external JIT like Pyjion changes the game. The window is closing to declare PyPy the successor to CPython2 before Python3 finds a way to steal the thunder and more people migrate from Python to new languages like Go or Python3. PyPy is a fantastic piece of technology that should take the forsaken mantle of Python2 for itself. Just needs a few political moves. PyPy is pure technological innovation. Python3 is pure technological churn and pure politics. You guys deserve the money and fame that will come with being the successor to Python2. Do it and good luck! [0]https://github.com/Microsoft/Pyjion

Thanks tanlermin. We are aware of nuitka and in general very excited about the various Turbo options that are showing up for Python. Our own effort is pyjion and we have a talk at PyCon 2016: https://github.com/Microsoft/Pyjion The high order bit is to restructure CPython to enable easy plugging in of various JIT optimizer/codegenerators into the interpreter. Our own attempt will be based on the cross-platform .Net JIT (generating machine code).