This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author rhettinger
Recipients docs@python, ezio.melotti, michael.foord, nedbat, pelson, rhettinger, terry.reedy, vinay.sajip
Date 2013-03-10.06:46:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362897976.94.0.646320503647.issue17351@psf.upfronthosting.co.za>
In-reply-to
Content
[Ned]
> Isn't it still good form to mention object as a base class.

I don't think so.  The classes look much cleaner without it.

+1 from for removing (object) from most examples (except for the descriptor howto).

[Terry]
> The respective howto and examples authors should give their 
> OK for deleting '(object)' in case they are trying to keep 
> one text compatible across 2 and 3. I added the other two 
> to the nosy list.

Thanks Terry.  Yes, I would like to keep (object) in the text of the descriptor how-to.  As you said, it keeps the text compatible.  But also, the explicit inheritance from (object) is an aid to clarity in a document that needs to highlight that attribute access occurs in two forms, object.__getattribute__ and type.__getattribute__.
History
Date User Action Args
2013-03-10 06:46:16rhettingersetrecipients: + rhettinger, terry.reedy, vinay.sajip, nedbat, ezio.melotti, michael.foord, docs@python, pelson
2013-03-10 06:46:16rhettingersetmessageid: <1362897976.94.0.646320503647.issue17351@psf.upfronthosting.co.za>
2013-03-10 06:46:16rhettingerlinkissue17351 messages
2013-03-10 06:46:16rhettingercreate