Har-de-har-har. If Adam was proposing "languages for good programmers," then languages out of Amsterdam or Zurich go too far to the other extreme and assume all programmers are incompetent morons who need a language that will protect them from themselves.
More seriously, though, I'm actually mostly OK with Python as another Algol 60 descendant. The past few decades have seen too much CompSci theory stuff (yes, I'm looking at you, lambda calculus) bolted on top of what could and should have remained simple imperative languages easily usable by the typical working programmer. But the guts of Python are just another way of expressing the usual core constructs: variables, conditionals, loops, blocks. Nothing all that crazy in the basics. Even the Modula-2/3 patois features are maybe defensible (and I didn't like Modula-2 back when I taught myself to use it); well-defined exception handling is useful.
That said, I am never going to think that indentation for scoping (or nesting, if one needs to be pedantic) is anything but a Guido van Rossumism -- a weird personal affectation, not a feature with enough real value to justify it over using visible symbols that clearly and unmistakably indicate scope opening and closing. I don't know if this is enough to keep me from using Python forever, but it certainly doesn't make me want to use it.
And note that I'm not saying the indentation-for-scoping thing has no value. I could argue that it might reduce errors slightly by letting the programmer see more code on the screen at one time (versus the Allman/GNU/Whitesmiths styles that put each brace on its own line). I once spent a couple of weeks working at AT&T Bell Labs in Naperville, and one of the things I enjoyed about that environment was that the monitors were much taller vertically than horizontally -- it felt useful to see more code on the screen than usual. If you (generic you) are the kind of coder who believes there's something magical about artificially keeping every function no larger than ten lines, then fewer curly braces on lines of their own might seem useful to you because you can see more actual working code that way.
For larger blocks, I think this value is outweighed by the cost of not clearly seeing where blocks begin and end by using specialized visible symbols to denote these intentions. Let me know when Python fixes that and I'll consider trying it.
(Note: Yes, I know you were just poking the bear; I had a few minutes of free time and felt like doing a little writing. If a bit of opinionizing will help keep this interesting conversation going, well, I'm happy to do my occasional part. )