Pyjion – A JIT for Python based upon CoreCLR
11–20 of 24 posts
Re: Pyjion – A JIT for Python based upon CoreCLR
#12Earlier quoted context omitted.
Exactly, we started on Windows out of ease-of-start/momentum. There are absolutely no plans to make this a Windows-exclusive. Basically we want to show this work pans out before working before putting in the work to make it cross-platform (we have an open issue to move to CMake to help solve the cross-platform problem: https://github.com/Microsoft/Pyjion/issues/76 ).
Exciting work! Is pyjion exploratory or is MS determined to see this through?
It's exploratory in the sense that we are seeing if this general approach works for CPython. But if this exploratory work shows promise, then we will see it through. And since I'm also a member of the Python development team I always want to see Python be faster and succeed more. :)
Re: Pyjion – A JIT for Python based upon CoreCLR
#13Earlier quoted context omitted.
Exciting work! Is pyjion exploratory or is MS determined to see this through?
Yes. :) It's exploratory in the sense that we are seeing if this general approach works for CPython. But if this exploratory work shows promise, then we will see it through. And since I'm also a member of the Python development team I always want to see Python be faster and succeed more. :)
Pyston seems to be catching up to PyPy fairly quickly ...not sure if there is anything transferable to pyjion, but if you haven't done so might be worth checking out.
Also for getting around the GIL, PyParallel seems to have a really interesting (and seemingly successful approach: http://pyparallel.org/
Its being worked on by one of the Guy's at continuum...and It's definitely in continuum's best interest to help python's future so I'm sure they wouldn't mind collab.
Re: Pyjion – A JIT for Python based upon CoreCLR
#14Earlier quoted context omitted.
It would also be nice if it worked outside of Windows.
if the speedups pan out, that is the plan! the work on performance has not been started yet however.
A while back there was some talk of native excel-python integration. Any chance that is in the pipes, or is MS sticking to R in that sense?
Re: Pyjion – A JIT for Python based upon CoreCLR
#15Re: Pyjion – A JIT for Python based upon CoreCLR
#16Earlier quoted context omitted.
Yes. :) It's exploratory in the sense that we are seeing if this general approach works for CPython. But if this exploratory work shows promise, then we will see it through. And since I'm also a member of the Python development team I always want to see Python be faster and succeed more. :)
Sweet, new Microsoft is awesome! Pyston seems to be catching up to PyPy fairly quickly ...not sure if there is anything transferable to pyjion, but if you haven't done so might be worth checking out. Also for getting around the GIL, PyParallel seems to have a really interesting (and seemingly successful approach: http://pyparallel.org/ Its being worked on by one of the Guy's at continuum...and It's definitely in cont…
Once we're back into Python, though, Pyjion's JIT'd version of whatever would kick in and do its thing. Perfect combo.
Re: Pyjion – A JIT for Python based upon CoreCLR
#17Re: Pyjion – A JIT for Python based upon CoreCLR
#18How does Pygion compare with IronPython?
IronPython is a re-implementation of Python in C# which allows it to play nice with .NET. This is similar to Jython which is a re-implementation of Python in Java that plays nice with the JVM.
This project on the other had is not a re-implementation at all, but aims to augment the existing CPython implementation with JIT APIs and is using CoreCLR for the JIT.
Re: Pyjion – A JIT for Python based upon CoreCLR
#19Earlier quoted context omitted.
if the speedups pan out, that is the plan! the work on performance has not been started yet however.
Awesome! A while back there was some talk of native excel-python integration. Any chance that is in the pipes, or is MS sticking to R in that sense?
Re: Pyjion – A JIT for Python based upon CoreCLR
#20Earlier quoted context omitted.
Yes. :) It's exploratory in the sense that we are seeing if this general approach works for CPython. But if this exploratory work shows promise, then we will see it through. And since I'm also a member of the Python development team I always want to see Python be faster and succeed more. :)
Sweet, new Microsoft is awesome! Pyston seems to be catching up to PyPy fairly quickly ...not sure if there is anything transferable to pyjion, but if you haven't done so might be worth checking out. Also for getting around the GIL, PyParallel seems to have a really interesting (and seemingly successful approach: http://pyparallel.org/ Its being worked on by one of the Guy's at continuum...and It's definitely in cont…
We are also aware of Pyston. There might be a chance that they could end up using our JIT hooks, but they also started a full year before us so they are not currently structured to plug into CPython like we're trying to through the API we're designing (although hopefully they will be able to, but who knows).