bpo-27931: Fix email address header parsing error#5329
Conversation
|
Hello, and thanks for your contribution! I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA). Unfortunately our records indicate you have not signed the CLA. For legal reasons we need you to sign this before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue. Thanks again to your contribution and we look forward to looking at it! |
| @@ -0,0 +1 @@ | |||
| Email parse IndexError <""@wiarcom.com> patch made by xiang.zhang | |||
There was a problem hiding this comment.
I suggest: Fix email address header parsing error when the username is an empty quoted string. Patch by xian.zhang.
|
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 |
|
did the change to the news file as requested |
| @@ -0,0 +1 @@ | |||
| Fix email address header parsing error when the username is an empty quoted string. Patch by xian.zhang. | |||
There was a problem hiding this comment.
Hmm, my name is Xiang Zhang.
|
fixed the typo in the name, sorry for not noticing the mistake |
|
@bitdancer: Please replace |
|
Thanks @jayyyin for the PR, and @bitdancer for merging it 🌮🎉.. I'm working now to backport this PR to: 3.6. |
Correctly handle addresses whose username is an empty quoted string. (cherry picked from commit aa218d1)
|
GH-5431 is a backport of this pull request to the 3.6 branch. |
https://bugs.python.org/issue27931
https://bugs.python.org/issue27931