[3.7] bpo-38332: Catch KeyError from unknown cte in encoded-word. (GH-16503) - #16597
Merged
Merged
Conversation
bedevere-bot
added
type-bug
Contributor
Author
1 similar comment
Contributor
Author
Member
|
@maxking, any reason to not merge this backport? |
maxking
approved these changes
Oct 12, 2019
Contributor
|
@ned-deily I was waiting for rc-period, but I guess I don't have to :) Merging this. |
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
6 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.
KeyError should cause a failure in parsing the encoded word and should be caught and raised as a _InvalidEWError instead.
(cherry picked from commit 65dcc8a)
Co-authored-by: Andrei Troie andreitroie90@gmail.com
https://bugs.python.org/issue38332