[issue795081] email.Message param parsing problem II

2016-12-12 Thread bpoaugust
bpoaugust added the comment: Rather that change unquote to deal with such malformed input, why not just enhance get/set boundary? That would reduce the impact of any changes. Also it should be easier to detect trailing rubbish in the value if you know it is a boundary value. -- nosy:

[issue795081] email.Message param parsing problem II

2015-06-13 Thread R. David Murray
R. David Murray added the comment: It think the thing to do is to turn it into a test case for both the old and the new parser, and the decide what we want the behavior to be. -- ___ Python tracker __

[issue795081] email.Message param parsing problem II

2015-06-12 Thread Milan Oberkirch
Milan Oberkirch added the comment: Is this still relevant? I just made a patch based on the suggestions discussed and it does not change the behavior of the original bug report (but fixed the bug regarding '' mentioned by tony_nelson). Maybe I'm missing something? -- keywords: +pat

[issue795081] email.Message param parsing problem II

2012-05-15 Thread R. David Murray
Changes by R. David Murray : -- assignee: r.david.murray -> components: +email ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue795081] email.Message param parsing problem II

2010-12-27 Thread R. David Murray
Changes by R. David Murray : -- versions: +Python 3.3 -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue795081] email.Message param parsing problem II

2010-05-05 Thread Barry A. Warsaw
Changes by Barry A. Warsaw : -- assignee: barry -> r.david.murray nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list m

[issue795081] email.Message param parsing problem II

2009-02-14 Thread Daniel Diniz
Daniel Diniz added the comment: Good candidate for the email sprint. Fix suggested inline. -- keywords: +easy nosy: +ajaksu2 stage: -> test needed versions: +Python 2.7 ___ Python tracker ___

[issue795081] email.Message param parsing problem II

2008-03-02 Thread Tony Nelson
Tony Nelson added the comment: If I understand RFC2822 3.2.2. Quoted characters (heh), unquoting must be done in one pass, so the current replace().replace() is wrong. It will change '\\"' to '"', but it should become '\"' when unquoted. This seems to work: re.sub(r'\\(.)',r'\1',s) I have