report at bugs
May 28, 2012, 11:40 AM
Post #1 of 1
(26 views)
Permalink
|
|
[issue975330] Inconsistent newline handling in email module
|
|
R. David Murray <rdmurray [at] bitdance> added the comment:
I almost applied this patch, but my gut is having second thoughts about it. I don't think this is the correct solution. The correct solution would be to delay the encoding of the body part until the message generation phase, and use the requested linesep at that point. That is, in 3.2 and 3.3 I've changed the paradigm from "always use \n and convert the final string at need" to "specify the linesep when flattening the message".
I'm uploading the completed patch here so I don't lose it, but I don't think I'm going to use it in this form.
----------
assignee: r.david.murray ->
components: +email -Library (Lib)
keywords: -easy, patch
stage: test needed -> needs patch
Added file: http://bugs.python.org/file25748/crlf_base64_body_encode.patch
_______________________________________
Python tracker <report [at] bugs>
<http://bugs.python.org/issue975330>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/list-python-bugs%40lists.gossamer-threads.com
|
