[3.10] bpo-44524: Do not set _name of _SpecialForm without need (GH-27861)#27871
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
) Because setting non-empty _name affects behavior of other code. In most cases __name__ can be derived from __origin__.__name__. (cherry picked from commit 4ceec49) Co-authored-by: Serhiy Storchaka <storchaka@gmail.com>
ContributorAuthor
miss-islington commented Aug 21, 2021
@serhiy-storchaka: Status check is done, and it's a success ✅ . |
serhiy-storchaka approved these changes Aug 21, 2021
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Because setting non-empty _name affects behavior of other code.
In most cases name can be derived from origin.name.
(cherry picked from commit 4ceec49)
Co-authored-by: Serhiy Storchaka storchaka@gmail.com
https://bugs.python.org/issue44524