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 cnicodeme
Recipients Dain Dwarf, Windson Yang, barry, bortzmeyer, cnicodeme, jpic, kal.sze, maxking, msapiro, ned.deily, nicoe, r.david.murray, vstinner, xtreak
Date 2019-07-03.07:17:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This thread has been really interesting to follow, I'm glad to have opened it :)

I would agree with Barry here, it should follow the documentation.

BUT, I would suggest to add a "strict" parameter that would throw exceptions depending on the parsing issue (missing a @, having multiple @, etc).

That way, a basic usage would return the empty strings, letting the developer know the email is invalid, and advanced case would still be possible.

By default, I think having strict set to False would be logical, since it would follow the documentation.
Date User Action Args
2019-07-03 07:17:23cnicodemesetrecipients: + cnicodeme, barry, vstinner, msapiro, ned.deily, r.david.murray, nicoe, maxking, kal.sze, Windson Yang, xtreak, bortzmeyer, jpic, Dain Dwarf
2019-07-03 07:17:23cnicodemesetmessageid: <>
2019-07-03 07:17:23cnicodemelinkissue34155 messages
2019-07-03 07:17:23cnicodemecreate