#25337: Validate domains against IDNA2008 instead of IDNA2003
----------------------------------+--------------------------------------
Reporter: JocelynD | Owner: nobody
Type: New feature | Status: closed
Component: Forms | Version: 1.8
Severity: Normal | Resolution: needsinfo
Keywords: domains idn idna | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Changes (by timgraham):
* status: new => closed
* type: Uncategorized => New feature
* resolution: => needsinfo
Comment:
Got only one response on the mailing list:
If I do not miss something, this is a "bug" in Python and not in Django.
However, I believe it could be good idea to have the 3rd-party idna
package as an optional dependency that Django makes use of if present but
works completely without it.
Closing this ticket as "needsinfo" absent a concrete proposal of how to
address this in Django. If someone is interested in this, please send your
proposal to the mailing list and we can reopen the ticket if it's
accepted.
--
Ticket URL: <https://code.djangoproject.com/ticket/25337#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.8dca79dfdbb434823c28a511e6c0c12a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
