Message96414
I perform a "grep" on the email package (with patch applied).
There's some places where 'raw-unicode-escape' is used.
I understand that all "payload.encode('raw-unicode-escape')" should be
changed to "payload.encode('ascii')" when the payload is processed by
another transfer encoding (line 202, 207 and 214).
The last one (when 'content-transfer-encoding' is not recognized) should
remain unchanged?
All other uses of 'raw-unicode-escape' seem correct.
Lib/email/base64mime.py:112:
return a2b_base64(string.encode('raw-unicode-escape'))
Lib/email/header.py:111:
word = bytes(word, 'raw-unicode-escape')
Lib/email/message.py:202:
payload = payload.encode('raw-unicode-escape')
Lib/email/message.py:207:
payload = payload.encode('raw-unicode-escape')
Lib/email/message.py:214:
in_file = BytesIO(payload.encode('raw-unicode-escape'))
Lib/email/message.py:225:
return payload.encode('raw-unicode-escape')
Lib/email/message.py:767:
as_bytes = charset[2].encode('raw-unicode-escape')
Lib/email/utils.py:298:
rawbytes = bytes(text, 'raw-unicode-escape') |
|
Date |
User |
Action |
Args |
2009-12-14 22:13:22 | flox | set | recipients:
+ flox, lemburg, barry, beazley, amaury.forgeotdarc, pitrou, vstinner |
2009-12-14 22:13:21 | flox | set | messageid: <1260828801.94.0.408596481981.issue4770@psf.upfronthosting.co.za> |
2009-12-14 22:13:17 | flox | link | issue4770 messages |
2009-12-14 22:13:17 | flox | create | |
|