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, r.david.murray, remi.lapeyre, skreft
Date 2018-11-13.17:48:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1542131326.95.0.788709270274.issue35222@psf.upfronthosting.co.za>
In-reply-to
Content
Because the RFCs are defined only for ascii.  Non-ascii in RFC 2822 addresses is an RFC violation.  In python2 non-ascii would usually round-trip through these functions, but again that was an accident.

If you'd like to propose a doc clarification that would be fine, but the clarification would be that behavior on strings containing non-ascii is undefined.

Note that these functions are considered soft-deprecated...they are in modules that are in the "Legacy API" section of the email docs.
History
Date User Action Args
2018-11-13 17:48:47r.david.murraysetrecipients: + r.david.murray, barry, skreft, remi.lapeyre
2018-11-13 17:48:46r.david.murraysetmessageid: <1542131326.95.0.788709270274.issue35222@psf.upfronthosting.co.za>
2018-11-13 17:48:46r.david.murraylinkissue35222 messages
2018-11-13 17:48:46r.david.murraycreate