[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

Change by Abhilash Raj : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: -Python 3.5, Python 3.6 ___ Python tracker ___ _

[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

miss-islington added the comment: New changeset e540bb546163f108c7c304f2e6865efaa78cd4c2 by Miss Islington (bot) in branch '3.8': bpo-38332: Catch KeyError from unknown cte in encoded-word. (GH-16503) https://github.com/python/cpython/commit/e540bb546163f108c7c304f2e6865efaa78cd4c2

[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

miss-islington added the comment: New changeset febe359559781019c0c8432a2f768809d00af6af by Miss Islington (bot) in branch '3.7': bpo-38332: Catch KeyError from unknown cte in encoded-word. (GH-16503) https://github.com/python/cpython/commit/febe359559781019c0c8432a2f768809d00af6af

[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

Change by miss-islington : -- pull_requests: +16185 pull_request: https://github.com/python/cpython/pull/16597 ___ Python tracker ___ __

[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

Change by miss-islington : -- pull_requests: +16184 pull_request: https://github.com/python/cpython/pull/16596 ___ Python tracker ___ __

[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

Abhilash Raj added the comment: New changeset 65dcc8a8dc41d3453fd6b987073a5f1b30c5c0fd by Abhilash Raj (Andrei Troie) in branch 'master': bpo-38332: Catch KeyError from unknown cte in encoded-word. (GH-16503) https://github.com/python/cpython/commit/65dcc8a8dc41d3453fd6b987073a5f1b30c5c0fd

[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

Emmanuel Arias added the comment: Hi Andrei sorry for my last message. Now I understand perfectly your idea and your PR. IMO this is a correct patch. -- ___ Python tracker __

[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

Andrei Troie added the comment: I agree with you that according to the RFC, the cte can of course only be "B" or "Q". My point is that, in my example, if you try to do that you get a KeyError propagating all the way down to email.message.get(), which I believe is incorrect. Consider an enc

[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

Change by Andrei Troie : -- keywords: +patch pull_requests: +16094 stage: -> patch review pull_request: https://github.com/python/cpython/pull/16503 ___ Python tracker ___ ___

[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

Emmanuel Arias added the comment: Hello, I am not a email expert, but according to RFC 1342 the enconding can be either "B" or "Q". So, I think is reasonable that when a not correct enconding is set, should be raise an exception I think that we can improve the message raising a more specif

[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

Change by Emmanuel Arias : -- nosy: +eamanu ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyth

[issue38332] invalid content-transfer-encoding in encoded-word causes KeyError

New submission from Andrei Troie : The following will cause a KeyError on email.message.get() import email import email.policy text = "Subject: =?us-ascii?X?somevalue?=" eml = email.message_from_string(text, policy=email.policy.default) eml.get('Subject') This is caused by the fact that the c