[issue20845] email.utils.formataddr encodes incorrectly

R. David Murray added the comment: Well, the "work around" was how you always had to do it in python2. So this is just a bit you can't port to the easier Python3 interface until you can drop python2 support. -- ___ Python tracker

[issue20845] email.utils.formataddr encodes incorrectly

Michael JasonSmith added the comment: I care enough to lodge an issue, but I lack the conviction in order to belabour the point in python-dev! I'll mark this issue as closed. Hopefully the work-around in my original post will help others :) -- resolution: -> wont fix status: open -> c

[issue20845] email.utils.formataddr encodes incorrectly

Changes by R. David Murray : -- components: +email nosy: +barry versions: -Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mai

[issue20845] email.utils.formataddr encodes incorrectly

R. David Murray added the comment: At the time we introduced this behavior in python3, it was considered an enhancement and thus not suitable for backporting. So you'd have to advocate for backporting it on python-dev. My guess is it won't be approved, especially since there are significant

[issue20845] email.utils.formataddr encodes incorrectly

New submission from Michael JasonSmith: The email.utils.formataddr function is used to encode a name-address 2-tuple for use as an email message. If the name contains a non-ASCII character it needs to be encoded. This happens correctly in Python 3.3.2, but incorrectly in Python 2.7.5. Ideally