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 ezio.melotti
Recipients docs@python, ezio.melotti, michael.foord, nedbat, pelson, rhettinger, terry.reedy, vinay.sajip
Date 2013-03-10.04:37:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362890254.46.0.976353470171.issue17351@psf.upfronthosting.co.za>
In-reply-to
Content
> Why is it important to remove subclassing object?

It's not /important/, but those are just leftovers from 2.x, and there's no reason to keep them around.

> Isn't it still good form to mention object as a base class.

I don't think so (or at least I've never seen anyone suggesting to keep or add "object" explicitly).

The patch LGTM, so unless there's a valid reason to keep the "object" around I'll commit it soon.
History
Date User Action Args
2013-03-10 04:37:34ezio.melottisetrecipients: + ezio.melotti, rhettinger, terry.reedy, vinay.sajip, nedbat, michael.foord, docs@python, pelson
2013-03-10 04:37:34ezio.melottisetmessageid: <1362890254.46.0.976353470171.issue17351@psf.upfronthosting.co.za>
2013-03-10 04:37:34ezio.melottilinkissue17351 messages
2013-03-10 04:37:34ezio.melotticreate