IMO, Python should only be used for what it was intended for: as a scripting language. I tend to use it as a kind of middle ground between shell scripting and compiled languages like Rust or C. It's a truly phenomenal language for gluing together random libraries and data formats, and whenever I have some one-off task where I need to request some data from some REST API, build a mapping from the response, categorize it, write the results as JSON, then push some result to another API -- I reach for Python.

But as soon as I have any suspicion that the task is going to perform any non-trivial computation, or when I notice the structure of the program starts to grow beyond a couple of files, that's when Python no longer feels suitable to the task.

Also great for rapid prototyping, but one needs to be real with oneself, it is a prototype.

I'd rather write python than rust personally, and I also don't mind if anything performance critical is written in rust.

Letting each language do what it does best is really ideal, I'm glad that python has a great FFI, I wish golang did.

Speaking of golang, the typescript compiler is now written in it. Another case of using each language for it's strengths.

Well Python isn't written in python either.

And it's killer use case today that is artificial intelligence development really uses it as a glue language for CUDA and similar GPU APIs.

CPython is written in C, but PyPy is written in RPython, at least.

Technically Python, the language spec, is written in English.

Try not to cut yourself while grinding that axe.

Python may not be the fastest language, but it's easy to learn, compilation times aren't an issue, you'll never have to fight the borrow checker, etc.

Every language has its warts.