>>19
What other languages?
Well, it's join(glue, pieces) in most and str.join(glue, pieces) is the same syntax. Alright, if you're obsessed and really really need it to be exactly join(glue, pieces) you can just do join=str.join .
>>20
Why does there have to be a distinction? [functions and methods]
There isn't, there's just a syntactical difference between class.func(obj, param) and obj.func(param) and Python allows you to use it either way, unlike other languages.
I've always found it hilarious how Pythonistas claim that Python is the opposite of TMTOWTDI
I'm a Pythonista and I support TMTOWTDI regardless of what others say. Remember Python is not some kind of cult, different people think differently. Whitespace is not here to kill TMTOWTDI, but to force morons to indent their code properly and avoid braces or BEGIN..END.
But wait, self doesn't have to be named self!
Exactly. We call it self because it's a nice name, but all it really is the first parameter.
Wait, you don't need to worry about those so-called private variables! Just access them with _classname__variable! Oh, and everything else is public, lollers! You don't need accessor methods, just change the variable directly! Oh, shit, did you just fuck up your refactoring by exposing internal implementation details?!
Python is a quality reflexive language. You *have* to be able to do that kind of thing. Besides, Python's OO is not paranoid like Java's, but more practical. You change properties directly because that's what properties are for. If the implementation changes and you really really need to change properties (which you shouldn't as often thanks to duck typing and because if you change it so much you probably need to change code which uses it), you can always override = and . . What else can you ask for? (Oh, and if you love useless work and ugly syntax, you can always define accessor methods. Nothing forbids them.)
PROTIP: If you like S&M, go back to Java. There you'll need to write 25-100 lines of interface for every class you create.
The syntax is full of fail, starting with __ and """
I agree that __ is excessive and Perl's recursive q<anything> quotes are much better.
trying to be corporate (lol zope)
I'm borderline offended by your statement :p
1. Zope is not Python
2. Zope sucks
>>24
Java is still sluggish at times because of its poor GC, and even compiled bytecode was shown to perform worse than Python in certain cases.
>>25
Yes, in your dreams Java boy.