Have you ever been fooled by incorrect indentation that didn't compile the way it looked?
Nope. My editor takes care of indentation for me, in every common language except Python, and when I have to deal with a batch of code written by someone else, I run it through indent(1) first. So, in fact, it's just the opposite: when the indentation doesn't match what I expect, I know there's an actual problem in the code!
With Python, on the other hand, I'm actually more likely to have an error in the indenting, because there's no easy way to see how many blocks I'm terminating when I outdent by an arbitrary amount. Which is a real PITA when you're refactoring.
Of course, things may be different if you're using crappy tools. But professionals shouldn't be using crappy tools.
Brackets, begin..end, and semicolons are crutches for compiler writers not programmers.
No, they're tools to make my job easier. Whatever the historical reason for them may be, they benefit the programmer! They make me more productive.
Now, I'll grant that Python is a remarkably good language despite its horrible flaw of relying on indentation. And many of its good features also make me more productive. But that doesn't mean that relying on the indentation isn't a horrible flaw.