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 steven.daprano
Recipients ju-sh, steven.daprano
Date 2020-03-21.13:06:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584795969.56.0.36292589814.issue40032@roundup.psfhosted.org>
In-reply-to
Content
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 clear;
- PEP 8 doesn't have an opinion on whether to explicitly or implicitly inherit from object;
- but the Zen of Python ("import this") does.

Do you have any good reasons for removing the explicit inheritance from object?
History
Date User Action Args
2020-03-21 13:06:09steven.dapranosetrecipients: + steven.daprano, ju-sh
2020-03-21 13:06:09steven.dapranosetmessageid: <1584795969.56.0.36292589814.issue40032@roundup.psfhosted.org>
2020-03-21 13:06:09steven.dapranolinkissue40032 messages
2020-03-21 13:06:09steven.dapranocreate