[jnxx]

I think the biggest drawback is a cultural one: The Python developers and the wider python community do not value backwards compatibility.

This has the consequence that it is easy to write new code, or to maintain short-lived code, like what is typical for a SAAS company or a start-up, but it will become almost impossible to maintain legacy code. And as Python becomes older, more and more of the total of Python code will become legacy code. The focus on writing new code rather than reading and maintaining old code is also very obvious by the befuddling added complexity of the language. Nobody knows all of C++, but I am not sure whether many Python developers know all of Python syntax and PEPs.

And what makes it even worse is that a lot of development in Python initially came from academic science and universities, like Numpy, but actually most scientific code is legacy code, because researchers and most research institutes operate differently from start-ups.