Mel <[EMAIL PROTECTED]> writes: >> I don't understand the purpose of this "correction". After all, >> __init__ *is* the closest equivalent to what other languages would >> call a constructor. > > Nevertheless, __init__ doesn't construct anything.
Only if by "construct" you mean "allocate". __init__ starts out with an empty object and brings it to a valid state, therefore "constructing" the object you end up with. That operation is exactly what other languages call a constructor. -- http://mail.python.org/mailman/listinfo/python-list
