Live data from Hacker News

Python JIT project was asked to pause development

discuss.python.org

1–10 of 105 posts

Re: Python JIT project was asked to pause development

#2
> For that reason, the Steering Council is formally requesting a Standards Track PEP be authored that the community can discuss and the Steering Council can formally accept (or reject), making the case for the JIT as a supported, non-experimental part of CPython: its guarantees, its maintenance commitments, and its impact on redistributors.

I didn't notice the current PEP was a provisional one. Hope the new one gets approved. The experimental JIT was reported to finally breaking even and surpassing the default interpreter just a couple of months ago[1].

[1] https://fidget-spinner.github.io/posts/jit-on-track.html

Re: Python JIT project was asked to pause development

#4
post #2

> For that reason, the Steering Council is formally requesting a Standards Track PEP be authored that the community can discuss and the Steering Council can formally accept (or reject), making the case for the JIT as a supported, non-experimental part of CPython: its guarantees, its maintenance commitments, and its impact on redistributors. I didn't notice the current PEP was a provisional one. Hope the new one gets…

>The experimental JIT was reported to finally breaking even and surpassing the default interpreter just a couple of months ago[1].

Thank You. As someone who don't follow python closely I thought their JIT would be similar to what Ruby has.

Not that Ruby YJIT or ZJIT is anywhere close to what JVM provides, but in this case it seems to be quite far ahead of Python.

Which is surprising given how many major companies are using Python. May be because those using Python are not using it as critical part of work unlike Shopify and Stripe which is their core language?

Re: Python JIT project was asked to pause development

#5
post #2

> For that reason, the Steering Council is formally requesting a Standards Track PEP be authored that the community can discuss and the Steering Council can formally accept (or reject), making the case for the JIT as a supported, non-experimental part of CPython: its guarantees, its maintenance commitments, and its impact on redistributors. I didn't notice the current PEP was a provisional one. Hope the new one gets…

Kind of a shit move to suddenly pull the rug once they've finally gotten it working. Should have been kept out of main from the start.

Re: Python JIT project was asked to pause development

#8
> While the intent is not to call for competing proposals, we believe that now is a good time to discuss and propose alternative proposals as well.

If I were a contributor I would read such language as saying "we have no respect for you or your intelligence, so we'll just straight up gaslight you and expect you to accept it."

The dictum can't be read literally - it has to be read like the manipulative, narcissist-speak that it is. And what it's telling you is - get out.

Re: Python JIT project was asked to pause development

#10
What a shame it will receive a halt when they where starting to make progress I know that after submitting the pep it will go back to development. But t would have been better to just keep the development and the pep for an actual release or continue and if gets rejected ask them to stop
Post reply on HN