class C: vs class C(object):
bruno.42.desthuilliers at wtf.websiteburo.oops.com
Fri Jul 20 11:40:01 CEST 2007
Aahz a écrit :
> In article <469f1557$0$26759$426a74cc at news.free.fr>,
> Bruno Desthuilliers <bruno.42.desthuilliers at wtf.websiteburo.oops.com> wrote:
>> To make a long story short: Python 2.2 introduced a new object model
>> which is more coherent and more powerful than the original one. The old
>> one was kept so far for compatibility reasons, but there's absolutely no
>> reason to use it no more since "new-style" classes can do anything
>> "Classic" classes did and much more. IOW, don't even bother with
>> old-style classes.
> And I'll make my usual knee-jerk response disagreeing with this. For
> more info, search groups.google.com.
And you'll still make it harder for newcomers to understand why a lot of
things don't work correctly with their classes. How helpful...
Aahz, the object model switch happened *years* ago, and it's quite clear
that old style classes have been kept so far for compatibility reasons
only. It's obvious that one doesn't gain *anything* - except compat with
years-old pre-2.2 versions of Python - using old-style classes. So *why*
on earth are you still *advocating* the use of old style classes ??????
More information about the Python-list