Message347157
| 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 | <1562103789.52.0.55680145594.issue34155@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
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? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-07-02 21:43:09 | barry | set | recipients: + 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:09 | barry | set | messageid: <1562103789.52.0.55680145594.issue34155@roundup.psfhosted.org> |
| 2019-07-02 21:43:09 | barry | link | issue34155 messages |
| 2019-07-02 21:43:09 | barry | create | |