[issue40032] Remove explicit inheriting of object in class definitions

Steven D'Aprano added the comment: On Sat, Mar 21, 2020 at 01:30:13PM +, 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 t

[issue40032] Remove explicit inheriting of object in class definitions

Karthikeyan Singaravelan added the comment: Previous discussion: https://bugs.python.org/issue17351 -- nosy: +xtreak ___ Python tracker ___ ___

[issue40032] Remove explicit inheriting of object in class definitions

Serhiy Storchaka added the comment: We usually do not accept mass cosmetic changes. It messes the history and may break pending PRs. It also consumes the time of core developers for review and has a risk of introducing bugs. -- nosy: +serhiy.storchaka resolution: -> rejected stage:

[issue40032] Remove explicit inheriting of object in class definitions

Julin added the comment: I just thought it looked different compared to the usual code that some of us were used to. Though it is probably familiar enough to the people who actually maintain the cpython code base. I agree with everything that you mentioned with regards to what I could under

[issue40032] Remove explicit inheriting of object in class definitions

Steven D'Aprano added the comment: Code churn for no good reason is not a good idea. I cannot think of any good reasons to change this: - it doesn't add new functionality; - it doesn't fix bugs; - it doesn't make the code easier to maintain; - it makes the code LESS clear instead of more clea

[issue40032] Remove explicit inheriting of object in class definitions

New submission from Julin : In the source, many class definitions still explicitly inherit from `object` though it is no longer necessary in Python3. Can't we change it? -- components: Library (Lib) messages: 364739 nosy: ju-sh priority: normal severity: normal status: open title: Rem