Very late post but I still have to add my $.02. I feel like your objection here is too strong and artificial.
I've used both Python and C-style languages including Go for a long time now (15 and 30+ years). I don't really mind either block system. I've had problems with editors doing unexpected things with Python code blocks, and I have to be watchful of that. But in practice I agree with the gp -- it's very rarely a problem except with beginners.
Curly braces are good for auto-formatting, and gofmt really seems to fit with the philosophy of Go in general, so I disagree with what Have is attempting to do in this case since I don't see how gofmt can do its job in this case. But I've also seen some really bad code with curly-braces. Recently I've had to work with a large (million lines) C++ code base that's completely inconsistent, mixing tabs and spaces with no one tab width making sense even within a single file. Every developer had their own editor and settings. Reading that was a major PITA and literally dozens of bugs ended up being wrong-code-block (indent level) types of bugs. And how often have you found yourself counting braces, brackets, and parentheses to find that balancing problem? That doesn't go away with Python, but it helps a little.
I also kind of hate this style that's so popular:
Reading lots of code written this way is significantly more taxing for me than the more compact styles, especially as outer blocks stretch out over multiple pages of text.
So: You have to be careful when editing indent-sensitive code like Python. But you also have to be careful when editing code with block delineators. Both styles can be bug-prone and are sensitive to accidental editor actions as well as mixed-developer consistency issues. For me the pros and cons of the two are closely balanced.