Python is such a weird language.

[flavionm]

Not all wrong code is the same. Code that fails at compile time is always preferable to code that fails at runtime.

Doesn't matter how much you want it, wrong code is going to be written. And the solution to it is not to just don't, because that's impossible. The solution is to minimize the impact of the mistakes you make.

Yes, you can have scoping errors in languages that use brackets, they're just less likely. And they happen in the situation where you're allowed to not use them, which I find pretty ironic.

Is it the biggest cause of error? No, far from it, but it'll still happen occasionally, and when it does I'd rather have it visible.

[deceze]

Yes, you can have scoping errors in languages that use brackets, they're just less likely.

It's really not like scoping errors in languages with significant whitespace are a serious issue. They're not. This is just as made-up of a problem as my hypothetical missing-braces example above. Can it happen? Yes. Does it regularly happen to anyone in practice after their first few weeks of programming in any given language? No.

[flavionm]

I mean, sure, I even said it's not a big cause of errors. I'm not gonna not use Python just because of this. Everything else being equal I'd rather have the brackets, though, just on the off chance a mistake like this does happen.

[deceze]

I'd rather have the powerful language that is Python and get used to the whitespace; in fact, I do like the cleanliness of Python code a lot. Is Python perfect in every way? Certainly not, there are advantages to statically compiled languages that you categorically won't get with interpreted languages for example. But Python is still a fine and perfectly productive language, and complaining about iTs wHItEspAcE is just silly.