summaryrefslogtreecommitdiffstats
path: root/Python/hashtable.c
diff options
context:
space:
mode:
authorArkadiusz Hiler <arek.l1@gmail.com>2020-05-14 00:53:26 (GMT)
committerGitHub <noreply@github.com>2020-05-14 00:53:26 (GMT)
commit6f2f475d5a2cd7675dce844f3af436ba919ef92b (patch)
treea716eac3e0f40024c90214076998a3b8a4b6609c /Python/hashtable.c
parent3d17c045b4c3d09b72bbd95ed78af1ae6f0d98d2 (diff)
downloadcpython-6f2f475d5a2cd7675dce844f3af436ba919ef92b.zip
cpython-6f2f475d5a2cd7675dce844f3af436ba919ef92b.tar.gz
cpython-6f2f475d5a2cd7675dce844f3af436ba919ef92b.tar.bz2
bpo-40597: email: Use CTE if lines are longer than max_line_length consistently (gh-20038)
raw_data_manager (default for EmailPolicy, EmailMessage) does correct wrapping of 'text' parts as long as the message contains characters outside of 7bit US-ASCII set: base64 or qp Content-Transfer-Encoding is applied if the lines would be too long without it. It did not, however, do this for ascii-only text, which could result in lines that were longer than policy.max_line_length or even the rfc 998 maximum. This changeset fixes the heuristic so that if lines are longer than policy.max_line_length, it will always apply a content-transfer-encoding so that the lines are wrapped correctly.
Diffstat (limited to 'Python/hashtable.c')
0 files changed, 0 insertions, 0 deletions