| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
This LGTM but it would be great if @ericvsmith could take a final look
Sorry, something went wrong.
|
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. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
There was a problem hiding this comment.
Seems this change also makes these methods pickleable.
Sorry, something went wrong.
| # Never overwrites an existing attribute. Returns True if the | ||
| # attribute already exists. | ||
| if isinstance(value, FunctionType): | ||
| value.__qualname__ = f"{cls.__qualname__}.{value.__name__}" |
There was a problem hiding this comment.
Why value.__name__ and not name? Are they always the same?
Sorry, something went wrong.
There was a problem hiding this comment.
For all use cases, but since it got extracted to another function which only takes cls and value, I guess there is no need to complicate that function.
Sorry, something went wrong.
Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
There was a problem hiding this comment.
👍
Sorry, something went wrong.
There was a problem hiding this comment.
With a few tiny issues, this looks good to me.
@serhiy-storchaka: Should we also add tests for pickling these methods? Or should that be another PR?
Sorry, something went wrong.
|
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. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. |
Sorry, something went wrong.
|
I do not think that it is necessary to add tests for pickling these methods. |
Sorry, something went wrong.
|
Sorry for the delays. This is on my list of things to look at next week during the development sprints. |
Sorry, something went wrong.
…ythonGH-22155) * bpo-41747: Ensure all dataclass methods uses their parents' qualname Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
| Back | FazBrowse Home | New Git URL |
https://bugs.python.org/issue41747