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
Unicode email address helper #40316
Comments
Converting email addresses between Unicode and ASCII is non |
Logged In: YES I think it is inappropriate to create new API for this. In addition, this patch lacks documentation and test cases. |
Logged In: YES Oops, test cases are there - only documentation is lacking. |
Logged In: YES I think that adding options to the existing APIs simply makes the Unicode I think the alternative approach would be to use a codec, similar to how I still prefer the OO approach though, as it allows the programmer to >>> e = EmailAddress(u'renee@ol\u00e9.de', u'Rene\u00e9 Acut\u00e9')
>>> e == str(e)
True
>>> e == unicode(e)
True
>>> e == str(EmailAddress(e.upper()))
True
>>> e == unicode(EmailAddress(e.upper()))
True |
I'm assigning this to myself so I don't lose it. I'll need to incorporate the intent of the tests and logic into email6. And yes I set 3.3 on purpose...email6 won't be in 3.2 and I don't want to spend the cycles figuring out whether this would work in email5 (the 3.2 version of email). |
bpo-1690608 addresses part of this issue, and bpo-11783 will address the IDNA part. From my point of view those two issues solve this problem from the perspective the email package infrastructure and *current* API. In the email6 API I do plan to have an address helper class that will make managing addresses more conveniently OO, but that is part of the whole email6 process and I don't feel a need any longer to keep this issue open. There's no good value for 'resolution' to express the resolution here (I've accepted the idea but not the code), so I used 'remind', since I will be coming back to the idea in a little while. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: