[issue25955] email.utils.formataddr does not support RFC 6532

Sergei Maertens added the comment: I could probably come up with a patch, but the reason I ran into this is because it's used in the core of Django. I already submitted a bug with Django, and with the legaciness of this function it feels like Django should move to the new API or implement its

[issue25955] email.utils.formataddr does not support RFC 6532

R. David Murray added the comment: formataddr is part of the legacy interface and has no knowledge of the current policy. So it doesn't support RFC 6532. For that you need to use the new API: just assign your address to the appropriate field, or create a headerregistry.Address object. I'm i

[issue25955] email.utils.formataddr does not support RFC 6532

Alessandro Cucci added the comment: Sergei can you submit a patch? Otherwise I can work on that, I have free time. -- nosy: +acucci ___ Python tracker ___ __

[issue25955] email.utils.formataddr does not support RFC 6532

Changes by Claude Paroz : -- nosy: +claudep ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue25955] email.utils.formataddr does not support RFC 6532

New submission from Sergei Maertens: The function `formataddr` in stdlib `email.utils` does not allow unicode e-mail addresses where the first part (before the @) is unicode. Python 3.5 promises support for SMTPUTF8 through `EmailPoliy.utf8` (https://docs.python.org/3/whatsnew/3.5.html#email),