flox <la...@yahoo.fr> added the comment:
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')
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue4770>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
