summaryrefslogtreecommitdiff
path: root/Lib/email/Encoders.py
diff options
context:
space:
mode:
authorBarry Warsaw <barry@python.org>2004-05-13 20:17:51 +0000
committerBarry Warsaw <barry@python.org>2004-05-13 20:17:51 +0000
commit4e59bc1e67e5459858d94b7e9fc41dfb0922ea62 (patch)
tree710616ad76c7806b6ae5d94d86b134096a95d275 /Lib/email/Encoders.py
parent58eb0fcb8f33e8bfd1f850f42c9efb27e1b48417 (diff)
downloadcpython-git-4e59bc1e67e5459858d94b7e9fc41dfb0922ea62.tar.gz
readline(): RFC 2046, section 5.1.2 (and partially 5.1) both state that the
parser must recognize outer boundaries in inner parts. So cruise through the EOF stack backwards testing each predicate against the current line. There's still some discussion about whether this is (always) the best thing to do. Anthony would rather parse these messages as if the outer boundaries were ignored. I think that's counter to the RFC, but might be practically more useful. Can you say behavior flag? (ug).
Diffstat (limited to 'Lib/email/Encoders.py')
0 files changed, 0 insertions, 0 deletions