On Tue, Aug 18, 2020 at 3:00 AM Christopher Barker
On Mon, Aug 17, 2020 at 8:42 AM Chris Angelico
but does it have a compatible API? If it does - if you can drop it in
and everything behaves equivalently - then it sounds like the sort of
thing that can be included in Python 3.10 with minimal fuss.
I’m confused - if it is fully compatible, then couldn’t it be included in all maintained versions of cPython?
Is anyone going to complain: “ hey! I just did a minor version update, and suddenly my program runs faster! WTF!”
OK: the obligatory XKCD:
In any case, a prototype outside of the cPython code base would be good for testing and review anyway.
That's exactly why it wouldn't be done in 3.9.1, even if it appears to be completely compatible. :) You never know what a change like this might break. This isn't purely an optimization, it's a complete replacement; but that should be safe for 3.10, just not for 3.9.1. ChrisA