Author steven.daprano
Recipients ju-sh, serhiy.storchaka, steven.daprano, xtreak
Date 2020-03-21.14:42:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20200321144100.GB4114@ando.pearwood.info>
In-reply-to <1584797413.91.0.674911861709.issue40032@roundup.psfhosted.org>
Content
On Sat, Mar 21, 2020 at 01:30:13PM +0000, Julin wrote:
> Why do you think it makes the code less clear, though?

Classes that inherit from object, and those which don't ("classic 
classes") behave differently in Python 2. But in Python 3, they are 
precisely the same.

Anyone who is familiar with Python 2, perhaps because they still have to 
deal with a legacy code base, or just because they learned using that 
version, will have to mentally adjust each time they see something which 
looks like a classic class, but actually is a new-style type.

Beginners who are only starting to learn Python may not understand the 
type hierarchy, and may believe that a class that doesn't explicitly 
inherit from object is a stand-alone class that doesn't inherit from 
object. Perhaps they have come from another language with different 
rules, or that lacks a single base object, like Python originally did.
History
Date User Action Args
2020-03-21 14:42:43steven.dapranosetrecipients: + steven.daprano, serhiy.storchaka, xtreak, ju-sh
2020-03-21 14:42:43steven.dapranolinkissue40032 messages
2020-03-21 14:42:43steven.dapranocreate