I agree, and I'm not advocating to freeze the python language, nor don't understand how understaffed the python core devs are. But there are strategies that ar

I agree, and I'm not advocating to freeze the python language, nor don't understand how understaffed the python core devs are. But there are strategies that are in used or have been in used that we could draw inspiration from: - async/await didn't need to become keywords so fast. True/False were not for 15 years. - changing the default encoding is behind env var flag. - changing the way the c api is done is currently made doing the separate HPy project. It's not breaking anything. So there were instances where people intelligently decided to move the language forward, but stopped and remembered Linus wisdom of "we don't breaking userland". And they did improve things without breaking others. Guido used to be very strict on that too. But after so many years, we can't expect him to spend all his energy still policing every aspect of the project, especially after he stepped down as a BDFL.