I think what Raymond Hettinger said is a good starting point: slow down and allow the ecosystem at large to catch up. Make big changes in a slower manner, and if there is no widespread agreement on a PEP for more than a year or two, just drop it.

1. I addressed this point by saying "I have no idea." I think the world has no idea. IEEE and other professional standards bodies are the only model I can think of, but it doesn't feel like a great fit. I tried to move the conversation forward. Maybe instead of challenging me, you could turn it into something actionable (or otherwise move the conversation forward). 2. Your "assertion" smacks a little of gaslighting. Python lies near the heart of the major Linux distributions that comprise, for example, AWS and Google Cloud. And they run services that directly or directly touch pretty much everyone in the industrialized world. Netflix by itself has 125M users, for example.

You claim that the python core team should be aware python is used by so many people, but you have no clue what them being deeply aware of that looks like, so how can you possibly claim that they're not doing that now, that doing so will make any difference, and that it's "forwards" for them to internalize that?

I also am absolutely floored that you'd pull out the term gaslighting for the parent comment which makes no assertions and only asks you to elaborate on your point more.

I think you need to step back, re-read this comment chain, and go look at a mirror.

Learn from Javascript. As a full stack dev who came to python only recently, I think Python could really learn from what's happening in the js ecosystem.

To make sure it does the opposite of anything the JS ecosystem ever did? In that case, I agree.

Don't know why you're being downvoted. As a Pythonista and author of a Python book, I'm really curious. Would you mind suggesting a few aspects of Javascript's ecosystem to look at?

Thanks in advance.