➜

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 r.david.murray
Recipients barry, karlcow, r.david.murray
Date 2013-04-11.19:53:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1365710016.15.0.615208197534.issue17369@psf.upfronthosting.co.za>
In-reply-to
Content 
It turns out the new header parsing code also missed this error recovery.  Or, rather, it recovers from it by completely ignoring the parameter with the bad syntax. 

I haven't worked out a solution that does more useful error recovery yet, but I'm posting an updated patch with tests for the new parser and something that may (or may not!) be heading in the direction of a fix, in case anyone else wants to work on it before I get back to it.
History
Date User Action Args
2013-04-11 19:53:36r.david.murraysetrecipients: + r.david.murray, barry, karlcow
2013-04-11 19:53:36r.david.murraysetmessageid: <1365710016.15.0.615208197534.issue17369@psf.upfronthosting.co.za>
2013-04-11 19:53:36r.david.murraylinkissue17369 messages
2013-04-11 19:53:36r.david.murraycreate