New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
__bases__ is a tuple (possibly empty or a singleton) #73198
Comments
The following statement is in the Language Reference for Custom classes:
AFAIK, I'm curious to see if this can actually be empty, if not, attached patch removes ''empty'' from the sentence. |
Most likely it just slipped through. In 2.7 the section is just called 'classes', not 'custom classes', and covered both classic classes and the new style classes that are all that python3 has. |
New changeset 721df314d45a by Berker Peksag in branch '3.5': New changeset 019125fb6d66 by Berker Peksag in branch '3.6': New changeset 454426dbff83 by Berker Peksag in branch 'default': |
Thanks, Jim. |
I think "possible a singleton" can be removed too. It doesn't add any useful information, any tuple is possible a singleton. |
Yes, I agree with that it seems redundant after the change. I'm attaching another small patch based on the committed one to trim that off. |
New changeset 1aba7cbbcc27 by Berker Peksag in branch '3.5': New changeset 7ef5b02b228a by Berker Peksag in branch '3.6': New changeset f05165a9cae6 by Berker Peksag in branch 'default': |
Good point, Serhiy. Thanks for the patch, Jim. I've now removed the "possible a singleton" part. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: