Message 55555 - 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	kael
Recipients	kael
Date	2007-09-01.08:56:58
SpamBayes Score	0.33671263
Marked as misclassified	No
Message-id	<1188637019.25.0.0476259625696.issue1079@psf.upfronthosting.co.za>
In-reply-to

Content
email.header.decode_header expect a space or end of line after the end of an encoded word ("?="). There is nothing about that thing in RFC 2047. Python 2.5.1 ChangeLog seems to indicate that this bug has been solved. Unfortunately, the function still don't work. A visible effet of the bad regex used has the consequence found in Issue 1467619 it seems there are 2 different regex with the same purpose in two different files (ecre in header.py & ecre in utils.py). the one in utils.py seems to give better results.

email.header.decode_header expect a space or end of line after the end
of an encoded word ("?="). There is nothing about that thing in RFC 2047.

Python 2.5.1 ChangeLog seems to indicate that this bug has been solved.
Unfortunately, the function still don't work.

A visible effet of the bad regex used has the consequence found in Issue
1467619

it seems there are 2 different regex with the same purpose in two
different files (ecre in header.py & ecre in utils.py). the one in
utils.py seems to give better results.

History
Date	User	Action	Args
2007-09-01 08:56:59	kael	set	spambayes_score: 0.336713 -> 0.33671263 recipients: + kael
2007-09-01 08:56:59	kael	set	spambayes_score: 0.336713 -> 0.336713 messageid: <1188637019.25.0.0476259625696.issue1079@psf.upfronthosting.co.za>
2007-09-01 08:56:59	kael	link	issue1079 messages
2007-09-01 08:56:58	kael	create