Message 60193 - 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.

Author	Sharebear
Recipients	Sharebear, barry, christian.heimes, loewis
Date	2008-01-19.16:48:11
SpamBayes Score	0.0006507889
Marked as misclassified	No
Message-id	<1200761292.88.0.717790928428.issue1823@psf.upfronthosting.co.za>
In-reply-to

Content
I'm beginning to realise this is slightly bigger than I first thought ;-) Trying to make a nice test case for this issue, I thought it would be a good idea for the parser to register a defect for invalid content- transfer-encoding so I can test against that in the test case rather than fragile substring tests. Unfortunately the parser code isn't the easiest code to get your head around on a first look.

I'm beginning to realise this is slightly bigger than I first thought
 ;-)

Trying to make a nice test case for this issue, I thought it would be a 
good idea for the parser to register a defect for invalid content-
transfer-encoding so I can test against that in the test case rather 
than fragile substring tests. Unfortunately the parser code isn't the 
easiest code to get your head around on a first look.

History
Date	User	Action	Args
2008-01-19 16:48:13	Sharebear	set	spambayes_score: 0.000650789 -> 0.0006507889 recipients: + Sharebear, loewis, barry, christian.heimes
2008-01-19 16:48:12	Sharebear	set	spambayes_score: 0.000650789 -> 0.000650789 messageid: <1200761292.88.0.717790928428.issue1823@psf.upfronthosting.co.za>
2008-01-19 16:48:11	Sharebear	link	issue1823 messages
2008-01-19 16:48:11	Sharebear	create