[Python-Dev] Pyston: a Python JIT on LLVM

Hi all, I'm excited to announce Pyston, a Python JIT under development at Dropbox, built on top of LLVM. You can read more about it at the introductory blog post, or check out the code on github

Re: [Python-Dev] Pyston: a Python JIT on LLVM

Kevin Modzelewski wrote: > Since it's the question that I think most people will inevitably (and > rightly) ask, why do we think there's a place for Pyston when there's PyPy > and (previously) Unladen Swallow? Have you seen Numba, the Python JIT that integrates with NumPy? http://numba.pydata.o

Re: [Python-Dev] Pyston: a Python JIT on LLVM

Hello, Le 03/04/2014 20:19, Kevin Modzelewski a écrit : I'm excited to announce Pyston, a Python JIT under development at Dropbox, built on top of LLVM. You can read more about it at the introductory blog post

Re: [Python-Dev] Pyston: a Python JIT on LLVM

On 04/04/2014 12:42 AM, Sturla Molden wrote: Kevin Modzelewski wrote: Since it's the question that I think most people will inevitably (and rightly) ask, why do we think there's a place for Pyston when there's PyPy and (previously) Unladen Swallow? Have you seen Numba, the Python JIT that in

Re: [Python-Dev] Pyston: a Python JIT on LLVM

Using optional type annotations is a really promising strategy and may eventually be added to Pyston, but our primary target right now is unmodified and untyped Python code. I think there's room for both approaches -- I think the "using type annotations to achieve near-native performance" can be v

Re: [Python-Dev] Pyston: a Python JIT on LLVM

On Fri, Apr 4, 2014 at 1:59 AM, Antoine Pitrou wrote: > > I'm a bit surprised by the approach. Why don't you simply process CPython > bytecode, rather than strive to reimplement Python fully? > The original choice to operate on Python AST rather than bytecode was made somewhat arbitrarily, but I

Re: [Python-Dev] Pyston: a Python JIT on LLVM

Kevin Modzelewski wrote: > Using optional type annotations is a really promising strategy and may > eventually be added to Pyston, but our primary target right now is > unmodified and untyped Python code What I meant to say is that Numba already has done the boiler-plate coding. Even if you use n