hklzr100

This is a good point. With tsan and helgrind multithreading becomes manageable in C/C++, nothing like that exists (or will exist) for Python.

Where is the progress? They claim "10-60%" improvements over Python 3.9 (I believe) and I don't notice much, partly because Python has always been sped up by C-extensions.

The price is an added complexity of the code base.

I truly don't understand why Python always gets a pass and people applaud every announcement, no matter how trivial or elusive it is.

The GIL effort is another matter. I'd rather have a simple interpreter with no-GIL than this mess of relatively small speedups.

But like other GvR efforts where he presided over a small group of people who did the work his efforts will of course go in. Like asyncio, the suboptimal "match" statement, the peg parser (which adds new workloads for other implementations because the de-facto DFL cannot be bothered with publishing an LALR grammar).

Python is a glue language, people can go elsewhere for speed.