>>18
elif is like Python's switch/case, only you can test for a completely different condition in it. Nothing bad with that.
>>20
um YES I have used python, how the fuck else could I comment on why it is BAD.
Most people who say forced intentation is bad are just people who had a quick look at Python, saw it, and thought "OMG RESTRICTIVE, OMG COBOL" without really giving it a try to discover it's easy to get used to and desirable afterwards. In fact, right now I'm fixing some PHP code and I'm wishing PHP had forced indentation because some lines are wrong and I don't like the braces convention used by this guy.
>>18
who is stoppping you doing
Not-forced-indentation is stopping me, because if I do that, there's no easy way to see the closing brace, and I can't be sure indentation is correct, unlike Python. That would work in a language with forced indentation, then again, when you have forced indentation you don't need braces.
>>22
Python doesn't force any programming paradigm into you, unlike pretty much anything else. It doesn't force shitUglyCase either. It doesn't force you to use tabs or spaces, and how many of them, not even to use the same amount of them, and never within parenthesized expressions or multiline quotes. It doesn't force you to not write shitty obfuscated code. The only thing it forces is to have some decency when writing blocks, so that you keep your code readable. That can't be bad.
Also,
>>24 pwned
>>22
>>25
Ah, semicolons. I don't mind them myself, but they are quite superfluous... I find JavaScript's a good solution for C-style languages with braces and shit: semicolons optional, you can use them when you need them, or everywhere. And in a language like Python, with indentation, you don't need them at all.