Author r.david.murray
Recipients Tim.Rawlinson, barry, docs@python, ezio.melotti, python-dev, r.david.murray
Date 2013-07-11.20:06:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1373573163.53.0.347259075375.issue18044@psf.upfronthosting.co.za>
In-reply-to
Content
This is actually two separate bugs, both a bit embarrassing.  The first one (that I just fixed) is that when parsing an encoded word I was only checking for decimal digits after an '=' (instead of the correct hex digits) when trying to do robust detection of encoded word limits.  

The second (the address one) is due to the fact that somewhere between stopping my full time work on the email project and actually committing the code, I lost track of the fact that I never implemented encoded word parsing for anything other than unstructured headers.  The infrastructure is there, I just need to write tests and hook it up.  

I'm going to open a separate issue for that.
History
Date User Action Args
2013-07-11 20:06:03r.david.murraysetrecipients: + r.david.murray, barry, ezio.melotti, docs@python, python-dev, Tim.Rawlinson
2013-07-11 20:06:03r.david.murraysetmessageid: <1373573163.53.0.347259075375.issue18044@psf.upfronthosting.co.za>
2013-07-11 20:06:03r.david.murraylinkissue18044 messages
2013-07-11 20:06:03r.david.murraycreate