[3.6] bpo-27931: Fix email address header parsing error (GH-5329)#5431
Merged
Conversation
Correctly handle addresses whose username is an empty quoted string. (cherry picked from commit aa218d1)
Contributor
Author
|
@jayyyin and @bitdancer: Backport status check is done, and it's a success ✅ . |
Member
|
@bitdancer I want to test out the commit co-author feature that GitHub just released: https://github.com/blog/2496-commit-together-with-co-authors Do you mind if I merge this PR myself? I'll try adding the co-author in the commit message and see if GitHub can preserve @jayyyin's info in the squash commit. |
Contributor
Author
|
Thanks, @Mariatta! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
Correctly handle addresses whose username is an empty quoted string.
(cherry picked from commit aa218d1)
https://bugs.python.org/issue27931