#17404: Email validator does not accept numeric TLD
-------------------------------------+-------------------------------------
Reporter: progval@… | Owner: nobody
Type: Bug | Status: reopened
Component: Core (Other) | Version: 1.3
Severity: Normal | Resolution:
Keywords: email validator | Triage Stage:
validation | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
I don't want to start a policy debate, but I have to point out that .42
only works for people who're using Global Anycast's DNS — in other words,
it doesn't work for something like 99.999% of Internet users (take or give
one 9).
The home page of Global Anycast (only available in French) says that the
next steps to help the project are "contribute to create a working proof
of concept" and "help define protocol v1". This indicates that the
projects is stil far from mainstream.
Given that this regex is subject to endless debates — see #17405, #17386,
#17100, #16310, and that's just from the first of the eleven pages of
[https://code.djangoproject.com/search?q=email+validator results for
"email validator"] — I'm reluctant to accept this ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/17404#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
