Thats the kind of abuse possible with languages such as Scala, Haskell or c++ templates.
That's the kind of abuse possible with languages such as Java.
---
Seriously. Every new API that you intend to use has a learning curve, some more significant than others. Every new API is a new "language".
If every API is a new language then you are doing it wrong - the API should respect the conventions of both the computer language it is in, and the domain-specific terminology of the domain it serves.
Seriously. You write your Java code, you compile it, and then in the night the evil AOP pixies sneak in and slip chunks of bytecode into your compiled classes.
If you'd said you worked on a 1MM LOC C++, Scala, or Perl project where you didn't have to establish strict coding standards to avoid the code base descending into madness, I'd be pretty shocked.
If you've worked on a 1MM SLOC project in any language where you didn't have to establish coding standards, you were exceptionally fortunate to have such a disciplined, single-minded team.
Python as a language does not lend itself to the same syntatic abuses...
Syntactic abuses are the least of my maintainability worries--if they're truly a factor in your development environment, you need to have a friendly discussion with the antisocial sociopaths who write deliberately obfuscated code.
Python's good at enforcing a particular indentation style. That's never been interesting to me with regard to coding standards.
I'd be interested to read more of your thinking in this matter.
The key factor is good people (this itself makes it not easy, sorry to disappoint.) If you have a competent team you don't need a dumbed down language to keep them in check.
If you have incompetent people, then you may use a restrictive language as a crutch. But don't expect good results.
I have a hard time swallowing the necessity to rely on restricting the expressive power of the language to prevent people from creating code that is hard to understand. My current project is in the order of 100 KLOC in Python (the horror, you can even redefine methods of single objects at runtime!) and so far none of the problems we've got can be tracked to language abuse.