diff options
| author | Barry Warsaw <barry@python.org> | 2002-05-19 23:51:50 (GMT) |
|---|---|---|
| committer | Barry Warsaw <barry@python.org> | 2002-05-19 23:51:50 (GMT) |
| commit | 7e21b6792babc785f96779d3881299ab643f7a1d (patch) | |
| tree | b9229713b8d3faa6b132764dc0bbe0c40704502f /Lib/test | |
| parent | 812031b95555e607ccec74f31aabc7601a53ed8a (diff) | |
| download | cpython-7e21b6792babc785f96779d3881299ab643f7a1d.zip cpython-7e21b6792babc785f96779d3881299ab643f7a1d.tar.gz cpython-7e21b6792babc785f96779d3881299ab643f7a1d.tar.bz2 | |
I've thought about it some more, and I believe it is proper for the
email package's Parser to handle the three common line endings.
Certain protocols such as IMAP define CRLF line endings and it doesn't
make sense for the client app to have to normalize the line endings
before handing it message off to the Parser.
_parsebody(): Be more flexible in the matching of line endings for
finding the MIME separators. Accept any of \r, \n and \r\n. Note
that we do /not/ change the line endings in the payloads, we just
accept any of those three around MIME boundaries.
Diffstat (limited to 'Lib/test')
0 files changed, 0 insertions, 0 deletions