summaryrefslogtreecommitdiff
path: root/Lib/email/header.py
diff options
context:
space:
mode:
authorINADA Naoki <methane@users.noreply.github.com>2017-10-04 12:47:38 +0900
committerGitHub <noreply@github.com>2017-10-04 12:47:38 +0900
commitbf477a99e0c85258e6573f4ee9eda68fa1f98a31 (patch)
tree89ada028feed7b97887303b872c7ddd5d1b8e9c4 /Lib/email/header.py
parente2d0dd2cf98cfa558435693b9f066edd7cf7d71a (diff)
downloadcpython-git-bf477a99e0c85258e6573f4ee9eda68fa1f98a31.tar.gz
bpo-31677: email: Remove re.IGNORECASE flag (GH-3868)
While there is not real bug in this case, using re.IGNORECASE without re.ASCII leads unexpected behavior. Instead of adding re.ASCII, this commit removes re.IGNORECASE flag because it's easier and simpler. This commit removes dead copy of the pattern in email.util module too. While the pattern is same, it is compiled separately because it had different flags.
Diffstat (limited to 'Lib/email/header.py')
-rw-r--r--Lib/email/header.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/Lib/email/header.py b/Lib/email/header.py
index c7b2dd9f31..7b30a039da 100644
--- a/Lib/email/header.py
+++ b/Lib/email/header.py
@@ -36,11 +36,11 @@ ecre = re.compile(r'''
=\? # literal =?
(?P<charset>[^?]*?) # non-greedy up to the next ? is the charset
\? # literal ?
- (?P<encoding>[qb]) # either a "q" or a "b", case insensitive
+ (?P<encoding>[qQbB]) # either a "q" or a "b", case insensitive
\? # literal ?
(?P<encoded>.*?) # non-greedy up to the next ?= is the encoded string
\?= # literal ?=
- ''', re.VERBOSE | re.IGNORECASE | re.MULTILINE)
+ ''', re.VERBOSE | re.MULTILINE)
# Field name regexp, including trailing colon, but not separating whitespace,
# according to RFC 2822. Character range is from tilde to exclamation mark.