Quoting this ticket: https://code.djangoproject.com/ticket/25337
""" IDNA domains validation is a mess, anyway, it's going forward, and IDNA2008 refines IDNA2003 proposal to better define what is a valid IDN domain and what is not. ICANN/IANA [ https://www.icann.org/resources/pages/idn-guidelines-2011-09-02-en recommends using IDNA2008] However, python standard lib [ https://docs.python.org/3/library/codecs.html?highlight=idna#module-encodings.idna only offers IDNA2003] validation in , and one have to use [ https://pypi.python.org/pypi/idna a 3rd party lib] to encode/validate against IDNA2008. Currently, on URLValidator, EmailValidator ([ https://code.djangoproject.com/ticket/18119 and soon DomainNameValidator ?]), Django relies on Python builtin `str.encode('idna')`. I don't come with a solution for Django, and I know that Django avoid to depend on 3rd-party libs. However I do think that it would be a good thing that Django validates domains against IDNA2008. What do you think? """ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" 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]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6d0523cc-1404-47e9-b777-4175030f9d3e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
