Do not use explicit inheritance from object in the documentation.#13936
Merged
serhiy-storchaka merged 1 commit intopython:masterfrom Jun 10, 2019
Merged
Conversation
0db3116 to
db99254
Compare
Contributor
|
FWIW, the explicit inheritance in the descriptor how-to was intentional. |
Member
Author
|
It was intentional in Python 2. But in Python 3 it just confuses readers and stays bad practice. I left the explicit inheritance in the case when it is used to explain the difference with the implicit inheritance (actually no difference). |
DinoV
pushed a commit
to DinoV/cpython
that referenced
this pull request
Jan 14, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.