#18119: add DomainNameValidator to validate Internet Domain Names
------------------------------+----------------------------------------
Reporter: michele | Owner: Nina Menezes
Type: New feature | Status: assigned
Component: Core (Other) | Version: dev
Severity: Normal | Resolution:
Keywords: validators | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
------------------------------+----------------------------------------
Comment (by mij):
The reason for adding accept_idna had nothing to do with how "modern" the
format was. It's a way to allow the developer to enforce ascii names.
Although python beautifully supports UTF, the developer is often required
to handle non-ascii characters specially. For example, when checking their
length, or storing them somewhere, or serializing them to somewhere else.
The exceeding rarity of IDNA causes many to assume the domain is ASCII,
only to run into exception later in production.
If not else, the presence of the accept_idna option forces the developer
to think whether that's a relevant case for them, and what to do about it.
I wouldn't necessarily consider adding it if the patch was without, but I
certainly see value in keeping it now it's already there.
PS: I'm the original submitter. Trac wouldn't send me a reset-password
link.
--
Ticket URL: <https://code.djangoproject.com/ticket/18119#comment:20>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018f9ad901c4-ef000205-2de6-40a8-900c-a88357e19c6f-000000%40eu-central-1.amazonses.com.
