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 msapiro
Recipients ajaksu2, barry, eric.araujo, msapiro, r.david.murray
Date 2010-07-17.14:07:20
SpamBayes Score 0.14639173
Marked as misclassified No
Message-id <>
> parsing 'merwok'
>  expected ('merwok', '')
>  got      ('', 'merwok')

I think ('', 'merwok') is the correct result. I think most if not all MUAs/MTAs will interpret an address without an '@', albeit invalid, as a local-part in the local domain, thus parsing 'merwok' as the address 'merwok' with no real name is probably the right thing to do with this input. The alternative would be to return ('', '') indicating failure.

> parsing 'merwok wok@rusty'
>  expected ('', 'wok@rusty')
>  got      ('', 'merwokwok@rusty')

Here, I think failure is a more appropriate return.

In any case, I think this is a new bug deserving of a new report. It is not really relevant to this issue which has to do with nested parentheses.
Date User Action Args
2010-07-17 14:07:24msapirosetrecipients: + msapiro, barry, ajaksu2, eric.araujo, r.david.murray
2010-07-17 14:07:24msapirosetmessageid: <>
2010-07-17 14:07:22msapirolinkissue1409460 messages
2010-07-17 14:07:21msapirocreate