Skip to content

bpo-27931: Fix email address header parsing error #5329

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

Merged
merged 5 commits into from
Jan 29, 2018

Conversation

jayyyin
Copy link
Contributor

@jayyyin jayyyin commented Jan 26, 2018

@jayyyin jayyyin requested a review from a team as a code owner January 26, 2018 01:51
@the-knights-who-say-ni
Copy link

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest: Fix email address header parsing error when the username is an empty quoted string. Patch by xian.zhang.

@bedevere-bot
Copy link

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.

@jayyyin
Copy link
Contributor Author

jayyyin commented Jan 26, 2018

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.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, my name is Xiang Zhang.

@jayyyin
Copy link
Contributor Author

jayyyin commented Jan 26, 2018

fixed the typo in the name, sorry for not noticing the mistake

@jayyyin jayyyin changed the title bpo-27931adding patch set 3 to master bpo-27931 Fix email address header parsing error Jan 26, 2018
@zhangyangyu zhangyangyu changed the title bpo-27931 Fix email address header parsing error bpo-2793: Fix email address header parsing error Jan 26, 2018
@zhangyangyu zhangyangyu changed the title bpo-2793: Fix email address header parsing error bpo-27931: Fix email address header parsing error Jan 26, 2018
@bitdancer bitdancer merged commit aa218d1 into python:master Jan 29, 2018
@bedevere-bot
Copy link

@bitdancer: Please replace # with GH- in the commit message next time. Thanks!

@miss-islington
Copy link
Contributor

Thanks @jayyyin for the PR, and @bitdancer for merging it 🌮🎉.. I'm working now to backport this PR to: 3.6.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Jan 29, 2018
Correctly handle addresses whose username is an empty quoted string.
(cherry picked from commit aa218d1)
@bedevere-bot
Copy link

GH-5431 is a backport of this pull request to the 3.6 branch.

Mariatta pushed a commit that referenced this pull request Jan 29, 2018
Correctly handle addresses whose username is an empty quoted string.
(cherry picked from commit aa218d1)

Co-authored-by: jayyyin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants