Python code written by mathematicians with scant regard for software design and maintainability.Leading to a big ball of mud.
Instead of using Deign Patterns to customise the application (ever heard of Strategy or Builder?) what happens is that the code is copied and modified., Now you two complete programs to maintains. Each new feature is a new program, and so on by mathematical induction.
People tend to compare languages based on many kinds of metrics, e.g. cute features, easy to use, functionality etc.
A possible bad scenario is Python code becoming unmaintainable because those writing the software (for example, applied mathematicians) have had no exposure to design principles of Design Patterns.
C++ v Python? the latter is (much) more difficult to maintain. And there's an associated price tag.
Corollary: discussions on software maintainability tend to fall on deaf ears.
People don't think like software engineers. It plays second fiddle to cute mathematical formulae.
Some perspectives on writing software:
An engineer, a software engineer, and a computer programmer are driving down the road when the car they are in gets a flat tire. The engineer says that they should buy a new car. The software engineer says they should sell the old tire and buy a new one. The computer programmer says they should drive the car around the block and see if the tire fixes itself.
Last but but not least, who pays the bill?