-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-40025: Require _generate_next_value_ to be defined before members #19098
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add a note in the docs about _generate_next_value_
needing to be defined before any members are.
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
Could this also have a test about the order raising TypeError? |
I have made the requested changes; please review again |
Thanks for making the requested changes! @ethanfurman: please review the changes made to this pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Getting closer -- thank you for persevering!
Misc/NEWS.d/next/Library/2020-03-21-05-26-38.bpo-40025.DTLtyq.rst
Outdated
Show resolved
Hide resolved
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
I have made the requested changes; please review again |
Thanks for making the requested changes! @ethanfurman: please review the changes made to this pull request. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! A couple minor changes and we should be good to go.
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase |
I have made the requested changes; please review again |
Thanks for making the requested changes! @ethanfurman: please review the changes made to this pull request. |
Thanks @ethanonstott for the PR, and @ethanfurman for merging it 🌮🎉.. I'm working now to backport this PR to: 3.8. |
Thanks @ethanonstott for the PR, and @ethanfurman for merging it 🌮🎉.. I'm working now to backport this PR to: 3.7. |
GH-19762 is a backport of this pull request to the 3.7 branch. |
…pythonGH-19098) require `_generate_next_value_` to be defined before members (cherry picked from commit d9a43e2) Co-authored-by: Ethan Onstott <storm@stormprograms.com>
…pythonGH-19098) require `_generate_next_value_` to be defined before members (cherry picked from commit d9a43e2) Co-authored-by: Ethan Onstott <storm@stormprograms.com>
GH-19763 is a backport of this pull request to the 3.8 branch. |
https://bugs.python.org/issue40025