Microsoft is starting its own JIT for Python.
Hello PyPy Team; I guess you guys already known. Microsft is starting its own pypy : https://github.com/Microsoft/Pyjion The main reason they mention there is due to weak CPyext support but It is just duplicating work, as you guys are already working on it . Shouldn't microsoft contribute into CPyext work in pypy instead? Regards, Phyo.
Isn't the blurb about PyPy now incorrect, with the cpyext advancements? """PyPy is an implementation of Python with its own JIT. The biggest difference compared to Pyjion is that PyPy doesn't support all C extension modules without modification unless they use CFFI or work with the select subset of CPython's C API that PyPy does support. Pyjion also aims to support many JIT compilers while PyPy only supports their custom JIT compiler.""" Eli On Thu, Jul 21, 2016 at 3:15 PM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:
Isn't the blurb about PyPy now incorrect, with the cpyext advancements? """PyPy is an implementation of Python with its own JIT. The biggest difference compared to Pyjion is that PyPy doesn't support all C extension modules without modification unless they use CFFI or work with the select subset of CPython's C API that PyPy does support. Pyjion also aims to support many JIT compilers while PyPy only supports their custom JIT compiler.""" Eli On Thu, Jul 21, 2016 at 3:15 PM, Phyo Arkar <phyo.arkarlwin@gmail.com> wrote:
participants (2)
-
Eli Stevens (Gmail) -
Phyo Arkar