The response at PyCon and EuroPython was pretty favorable, and a lot of core devs seem into it. This is definitely gonna happen unless something big comes up.
There was still a bit of discussion about the exact form (3.26 vs 3.2026 etc), but that is handled and I expect it to be on the standards track soon.
Next year. It’s a yearly release cadence.
Also, 3.14 will be the last one in this version numbering scheme. The one after that will be 3.26.
Python has gotten faster, but it’s still nowhere near what you expect from traditional compiled languages. It can’t be.
The trick to writing performant Python code is to get good (native) libraries and let it handle the heavy lifting.
For performance sensitive stuff, the fact that pure Python is very slow really matters. For stuff that’s not performance sensitive (that is, 99% of the code out there) it doesn’t really matter, but even then it’s better to be fast than to be slow.
Now this is not something I would ordinarily have a problem with. I use Python for a reason and it’s not performance. But if I end up writing Python like it’s rust, I might as well do rust and reap the (massive!!!) performance and memory profile benefits too while I’m at it.
My main issue is that you’re going through all that trouble and still get Python-level performance.
I really like Python, but there are better typed languages out there. Also, faster ones.
And thank god for that. Theoretical computer science is still good ;)