Miss Islington (bot) ffe9ba0477 [3.12] gh-92081: Fix for email.generator.Generator with whitespace between encoded words. (GH-92281) (#119246) ... * Fix for email.generator.Generator with whitespace between encoded words. email.generator.Generator currently does not handle whitespace between encoded words correctly when the encoded words span multiple lines. The current generator will create an encoded word for each line. If the end of the line happens to correspond with the end real word in the plaintext, the generator will place an unencoded space at the start of the subsequent lines to represent the whitespace between the plaintext words. A compliant decoder will strip all the whitespace from between two encoded words which leads to missing spaces in the round-tripped output. The fix for this is to make sure that whitespace between two encoded words ends up inside of one or the other of the encoded words. This fix places the space inside of the second encoded word. A second problem happens with continuation lines. A continuation line that starts with whitespace and is followed by a non-encoded word is fine because the newline between such continuation lines is defined as condensing to a single space character. When the continuation line starts with whitespace followed by an encoded word, however, the RFCs specify that the word is run together with the encoded word on the previous line. This is because normal words are filded on syntactic breaks by encoded words are not. The solution to this is to add the whitespace to the start of the encoded word on the continuation line. Test cases are from GH-92081 * Rename a variable so it's not confused with the final variable. (cherry picked from commit a6fdb31b67) Co-authored-by: Toshio Kuratomi <a.badger@gmail.com>		2024-05-20 20:10:49 +00:00
..
data	[3.12] gh-106186: Don't report MultipartInvariantViolationDefect for valid multipart emails when parsing header only (GH-107016) (#107111)	2023-07-23 14:28:28 +02:00
__init__.py	bpo-43651: PEP 597: Fix test_email (GH-25158)	2021-04-05 12:30:12 +09:00
__main__.py
test__encoded_words.py	bpo-43323: Fix UnicodeEncodeError in the email module (GH-32137)	2022-04-30 13:17:23 +03:00
test__header_value_parser.py	[3.12] bpo-40944: Fix IndexError when parse emails with truncated Message-ID, address, routes, etc (GH-20790) (GH-117974)	2024-04-23 20:50:43 +03:00
test_asian_codecs.py	Merge with 3.5	2016-05-06 17:35:21 -04:00
test_contentmanager.py	bpo-41402: Fix email ContentManager calling .encode() on bytes (GH-21631)	2021-08-09 18:45:41 +02:00
test_defect_handling.py	bpo-27397: Make email module properly handle invalid-length base64 strings (#7583)	2018-06-12 15:46:22 +03:00
test_email.py	[3.12] gh-80361: Fix TypeError in email.Message.get_payload() (GH-117994) (GH-117998)	2024-04-17 16:59:35 +00:00
test_generator.py	[3.12] gh-92081: Fix for email.generator.Generator with whitespace between encoded words. (GH-92281) (#119246)	2024-05-20 20:10:49 +00:00
test_headerregistry.py	[3.12] gh-92081: Fix for email.generator.Generator with whitespace between encoded words. (GH-92281) (#119246)	2024-05-20 20:10:49 +00:00
test_inversion.py	bpo-30681: Support invalid date format or value in email Date header (GH-22090)	2020-10-26 17:31:06 -07:00
test_message.py	[3.12] gh-94606: Fix error when message with Unicode surrogate not surrogateescaped string (GH-94641) (GH-112971)	2023-12-11 16:48:06 +00:00
test_parser.py	#20476: add a message_factory policy attribute to email.	2016-09-09 18:39:18 -04:00
test_pickleable.py
test_policy.py	[3.12] gh-77749: Fix inconsistent behavior of non-ASCII handling in EmailPolicy.fold() (GH-6986) (GH-114606)	2024-01-26 18:30:32 +02:00
test_utils.py	[3.12] gh-113027: Fix test_variable_tzname in test_email (GH-113821) (GH-113831)	2024-01-12 12:00:17 +00:00
torture_test.py	bpo-5846: Do not use obsolete unittest functions. (GH-28303)	2021-09-13 10:49:53 +03:00