-
-
Notifications
You must be signed in to change notification settings - Fork 32.3k
bpo-35899: Fix Enum handling of empty and weird strings #11891
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
Co-authored-by: Maxwell <[email protected]> Co-authored-by: Stéphane Wirtel <[email protected]>
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.
LGTM
Thank you for your contribution.
@ethanfurman do you want to review/merge this PR? Have a nice day, |
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 pretty good! A couple more changes and this should be ready 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 |
…tyAndNonLatinStrings
I have made the requested changes; please review again Thank you, Ethan. I've updated both files accordingly. |
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.
One more minor change and this PR is good to go! Nice work!
Misc/NEWS.d/next/Library/2019-02-16-07-11-02.bpo-35899.cjfn5a.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 |
@bdbaraban: Status check is done, and it's a success ✅ . |
Thanks @bdbaraban for the PR 🌮🎉.. I'm working now to backport this PR to: 3.6, 3.7. |
Co-authored-by: Maxwell <[email protected]> Co-authored-by: Stéphane Wirtel <[email protected]> https://bugs.python.org/issue35899 (cherry picked from commit 8b914d2) Co-authored-by: Brennan D Baraban <[email protected]>
GH-12150 is a backport of this pull request to the 3.7 branch. |
GH-12151 is a backport of this pull request to the 3.6 branch. |
Co-authored-by: Maxwell <[email protected]> Co-authored-by: Stéphane Wirtel <[email protected]> https://bugs.python.org/issue35899 (cherry picked from commit 8b914d2) Co-authored-by: Brennan D Baraban <[email protected]>
Co-authored-by: Maxwell <[email protected]> Co-authored-by: Stéphane Wirtel <[email protected]> https://bugs.python.org/issue35899 (cherry picked from commit 8b914d2) Co-authored-by: Brennan D Baraban <[email protected]>
Co-authored-by: Maxwell [email protected]
Co-authored-by: Stéphane Wirtel [email protected]
https://bugs.python.org/issue35899