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 barry
Recipients Dain Dwarf, Windson Yang, barry, bortzmeyer, cnicodeme, jpic, kal.sze, maxking, msapiro, ned.deily, nicoe, r.david.murray, vstinner, xtreak
Date 2019-07-02.21:43:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I still think the only way to read the documentation for parseaddr('a@b@c') is to return ('', '') - a tuple of empty strings.

The documentations says:

"Returns a tuple of that information, unless the parse fails, in which case a 2-tuple of ('', '') is returned."

Of course, it doesn't define exactly what a "failing parse" is, but I would claim that a non-RFC compliant address should fail to parse, at least for the parseaddr() interface.

I'm not concerned about inconsistencies between message_from_string() and parseaddr().  They are difference APIs.

I'll follow up on the PR, but does anybody disagree with that reasoning?
Date User Action Args
2019-07-02 21:43:09barrysetrecipients: + barry, vstinner, msapiro, ned.deily, r.david.murray, nicoe, maxking, kal.sze, Windson Yang, xtreak, cnicodeme, bortzmeyer, jpic, Dain Dwarf
2019-07-02 21:43:09barrysetmessageid: <>
2019-07-02 21:43:09barrylinkissue34155 messages
2019-07-02 21:43:09barrycreate