-
-
Notifications
You must be signed in to change notification settings - Fork 33.4k
bpo-33175: dataclasses should look up __set_name__ on class, not instance #6305
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
bpo-33175: dataclasses should look up __set_name__ on class, not instance #6305
Conversation
|
@JelleZijlstra, can you take a look? |
| @@ -0,0 +1,2 @@ | |||
| In dataclasses, Field.__set_name__ now looks up the __set_name__ special | |||
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.
Does this need a NEWS entry if there was no release with the buggy code? (I'm mostly curious; you'll know the norms better than I do.)
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.
I thought about this, but unfortunately I think it does need the NEWS blurb. Ned has already cut 3.7.0b3, so the bug will be in that release. Thanks again for catching this.
|
Thanks @ericvsmith for the PR 🌮🎉.. I'm working now to backport this PR to: 3.7. |
|
GH-6309 is a backport of this pull request to the 3.7 branch. |
…ance (pythonGH-6305) (cherry picked from commit 5219952) Co-authored-by: Eric V. Smith <[email protected]>
…ance (GH-6305) (cherry picked from commit 5219952) Co-authored-by: Eric V. Smith <[email protected]>
https://bugs.python.org/issue33175