#33968: Make EmailValidator and URLValidator IDNA 2008 compliant
-------------------------------------+-------------------------------------
Reporter: j-bernard | Owner: nobody
Type: New feature | Status: closed
Component: Core (Other) | Version: 4.0
Severity: Normal | Resolution: wontfix
Keywords: IDNA EAI | Triage Stage:
EmailValidator UrlValidator RFC | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* cc: Florian Apolloner (added)
* resolution: => wontfix
* status: new => closed
* component: Core (Mail) => Core (Other)
* type: Uncategorized => New feature
Comment:
Thanks for this ticket, however adding a new dependency is always
controversial and it isn't a light decision so a strong consensus on the
mailing list is required. Please first start a discussion on the
DevelopersMailingList, where you'll reach a wider audience and see what
other think, and
[https://docs.djangoproject.com/en/stable/internals/contributing/bugs-and-
features/#requesting-features follow the guidelines with regards to
requesting features].
Personally, I don't think it's worth complexity. My initial response would
be similar to the Python's, i.e. ''"If you need the IDNA 2008 standard
from RFC 5891 and RFC 5895, use a third-party validator"''.
--
Ticket URL: <https://code.djangoproject.com/ticket/33968#comment:1>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070182f0666eff-00f7f691-a1e5-4566-aa32-a194341d73ac-000000%40eu-central-1.amazonses.com.
