-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-36470: Allow dataclasses.replace() to work InitVar with default values #17441
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-36470: Allow dataclasses.replace() to work InitVar with default values #17441
Conversation
Misc/NEWS.d/next/Library/2019-12-02-21-03-41.bpo-36470.Gy9Sff.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 |
…alues If a dataclass contain an InitVar, that InitVar must be specified in the call to replace(), unless it has a default value, in which case replace() should not raise a `ValueError` if the value was not specified in the call to replace(). Patch by Claudiu Popa.
8dc7351
to
2dca685
Compare
Hi @ericvsmith Thank you for the review! Sorry about that I have made the requested changes; please review again. |
Thanks for making the requested changes! @ericvsmith: please review the changes made to this pull request. |
I see https://bugs.python.org/issue36470 is still open. Why was this PR closed without a merge? |
I don't know why it was closed. I'll try and take a look at the bpo. |
any news on this? I just hit this issue myself and wound up here |
If a dataclass contain an InitVar, that InitVar must be specified in the call to replace(), unless it has a default value, in which case replace() should not raise a
ValueError
if the value was not specified in the call to replace().https://bugs.python.org/issue36470