-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some email addresses are messed up with parse_email=False #60
Comments
This only occurs with |
Sounds like a good workaround. However, why not always parse email but simply do not modify them if |
That's an interesting idea but I really want to get 1.2 out, so I'm going to bump to 1.3 and see if that's a good path to follow. |
I have a similar problem when setting parse_email=False. Any email with following the pattern something.tlds@somedomain.something where tlds is For example...
becomes...
But...
is fine, since "coops" isn't in |
I'm going to drop this from the milestone. I think it needs more thinking and I'm not going to get to it for v2.0. |
I spent some time fiddling with this today. If we always parse out email addresses, but have
I don't think we can get both cases to work without a rewrite of some kind, but I'm not sure what that would look like. I don't know how to fix this and I'm not that interested in spending more time on it. If someone else wants, they should take a stab at it and let us know what they find. Otherwise, I'll probably close it out because it's been open for 6 years and no one seems interested enough to look into it further. |
This is a problem, but this isn't something we're going to fix. Sorry! |
The text was updated successfully, but these errors were encountered: