Ville Lindholm <ville.lindh...@gmail.com> added the comment:
I tried doing a naive implementation (just checking for \n or \r in the
argument to Header) but that breaks a lot of unit tests. For example the test
message msg_16.txt contains a header like this:
Received: from cougar.noc.ucla.edu (cougar.noc.ucla.edu [169.232.10.18])
by babylon.socal-raves.org (Postfix) with ESMTP id CCC2C51B84
for <scr-ad...@socal-raves.org>; Sun, 23 Sep 2001 20:13:54 -0700 (PDT)
in other words the header is split up by \n\t. I'm not very familiar with the
RFCs, is there some smart way to do this? (This is my first attempt to
contribute to Python btw!) It seems many tests rely on this "bug" in Header.
----------
nosy: +vvl
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue5871>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
