[Python-Dev] Re: Contributing the Pyston jit?

Ah ok thanks for the tip, I re-posted this as https://discuss.python.org/t/contributing-the-pyston-jit/24195 On Thu, Feb 23, 2023 at 6:02 PM Brett Cannon wrote: > FYI you will probably get more engagement if you posted this to > discuss.python.org . > > On Thu, Feb 23, 2023, 10:18 Kevin Modzelew

[Python-Dev] Re: Contributing the Pyston jit?

FYI you will probably get more engagement if you posted this to discuss.python.org . On Thu, Feb 23, 2023, 10:18 Kevin Modzelewski wrote: > Hello all, we on the Pyston team would like to propose the contribution of > our JIT >

[Python-Dev] Re: Contributing the Pyston jit?

On Thu, Feb 23, 2023, 11:34 Wes Turner wrote: > Please consider colesbury/nogil in rebasing? > https://github.com/colesbury/nogil > It's very premature for anyone to concern themselves with Sam's nogil work when it comes to their own work as PEP 703 has not been sent to the SC (let alone been ac

[Python-Dev] Re: Contributing the Pyston jit?

Please consider colesbury/nogil in rebasing? https://github.com/colesbury/nogil On Thu, Feb 23, 2023, 1:20 PM Kevin Modzelewski wrote: > Hello all, we on the Pyston team would like to propose the contribution of > our JIT >

[Python-Dev] Contributing the Pyston jit?

Hello all, we on the Pyston team would like to propose the contribution of our JIT into CPython main. We're interested in some initial feedback on this idea before putting in the work to rebase the jit to 3.12 for a PEP and