#21859: clarify Django docs re: email addresses and ascii
-------------------------------------+------------------------------------
Reporter: cjerdonek | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.6
Severity: Normal | Resolution:
Keywords: email,ascii,unicode | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+------------------------------------
Comment (by claudep):
RFC 6531 does define a new SMTPUTF8 extension
(http://tools.ietf.org/html/rfc6531) to allow (notably) non-ASCII chars in
email addresses. Usage seems to be very scarce however at this time.
Allowing non-ASCII chars when 95% of mail servers do currently not seem to
support that is debatable.
What could be done is to create a new `validate_email_utf8` validator, and
maybe add a new `support_utf8` argument to `EmailField`, or add an
`addr_validator` argument to `EmailField` (defaulting to the legacy
`validate_email` validator), so as user can choose themselves if they want
to allow that usage or not without having to subclass `EmailField`
altogether.
--
Ticket URL: <https://code.djangoproject.com/ticket/21859#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.42f555eced9a7786aa7a6bcb250ab7b9%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
