>>7
Later on in life, they move out, and start to fend for themselves, and they realize, hey, if I want cookies for dinner, I'll have cookies for dinner.
Not in my house, not in my development team. The cookies example is not really valid, because if you have cookies for dinner, you're just hurting yourself by becoming a fat American, but if somebody in my team doesn't indent his code, he'll be fucking with me when I have to read and fix his crap.
If you want to write quick hacks and find Python very uncomfortable, use Perl. For real work, there's a language where you know you won't have to deal with morons' code.
The forced indentation of code is a non-issue. If you write proper code, it doesn't bother you in the very least, because you're already indenting it. It comes at no cost; it's not like static typing or anything that could be seen as a pain in the ass. OTOH, if you write shittily, it does you and others good by forcing you to work properly.
I'm far more willing to maintain Python code than any other language, not only because it's guaranteed to be properly indented, but because the forced indentation of code keeps Perl and similar faggots away. It's the same reason why Linux Tarballs would choose C: besides of the language's benefits, it's good because it keeps C++ faggots away.