Message 113157 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	vvl
Recipients	barry, jwilk, pl, r.david.murray, terry.reedy, vvl
Date	2010年08月07日.09:23:55
SpamBayes Score	0.0006873462
Marked as misclassified	No
Message-id	<1281173037.5.0.372744406311.issue5871@psf.upfronthosting.co.za>

Content
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-admin@socal-raves.org>; 2001年9月23日 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.

Content

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-admin@socal-raves.org>; 2001年9月23日 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.

History
Date	User	Action	Args
2010年08月07日 09:23:57	vvl	set	recipients: + vvl, barry, terry.reedy, jwilk, pl, r.david.murray
2010年08月07日 09:23:57	vvl	set	messageid: <1281173037.5.0.372744406311.issue5871@psf.upfronthosting.co.za>
2010年08月07日 09:23:56	vvl	link	issue5871 messages
2010年08月07日 09:23:55	vvl	create

homepage