➜

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 Sergei Maertens, acucci, barry, claudep, r.david.murray
Date 2015-12-26.15:48:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1451144880.96.0.609268264311.issue25955@psf.upfronthosting.co.za>
In-reply-to
Content 
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 in the process of rewriting the docs to make all of this clear, but, well, I'm slow...
History
Date User Action Args
2015-12-26 15:48:00r.david.murraysetrecipients: + r.david.murray, barry, claudep, acucci, Sergei Maertens
2015-12-26 15:48:00r.david.murraysetmessageid: <1451144880.96.0.609268264311.issue25955@psf.upfronthosting.co.za>
2015-12-26 15:48:00r.david.murraylinkissue25955 messages
2015-12-26 15:48:00r.david.murraycreate