Skip to content

[3.8] bpo-38698: Add a new InvalidMessageID token to email header parser. (GH-17503) #17514

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 1 commit into from
Dec 9, 2019

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Dec 9, 2019

This adds a new InvalidMessageID token to the email header parser which can be
used to represent invalid message-id headers in the parse tree.
(cherry picked from commit 68157da)

Co-authored-by: Abhilash Raj maxking@users.noreply.github.com

https://bugs.python.org/issue38698

…ythonGH-17503)

This adds a new InvalidMessageID token to the email header parser which can be
used to represent invalid message-id headers in the parse tree.
(cherry picked from commit 68157da)

Co-authored-by: Abhilash Raj <maxking@users.noreply.github.com>
@miss-islington
Copy link
Contributor Author

@maxking: Status check is done, and it's a success ✅ .

@miss-islington miss-islington merged commit f66f4a0 into python:3.8 Dec 9, 2019
@miss-islington miss-islington deleted the backport-68157da-3.8 branch December 9, 2019 02:11
@miss-islington
Copy link
Contributor Author

@maxking: Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
Contributor Author

@maxking: Status check is done, and it's a success ✅ .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-bug An unexpected behavior, bug, or error
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants