#27029: Make EmailValidator accept non-ASCII characters
-------------------------------------+-------------------------------------
Reporter: Ramin Farajpour | Owner: j-bernard
Cami |
Type: | Status: assigned
Cleanup/optimization |
Component: Core (Other) | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* needs_better_patch: 0 => 1
Comment:
> My suggestion would then be to make the default validator more
permissive to get some flexibility in the kind of use case that I have.
One can still include another validation layer on top of that.
I don't think we can just swap out the current validation for a looser
one. Folks will be depending on the existing behaviour.
Maybe we can ship a couple of variants, but I'm not sure what switching
method we might allow. I think we need a story there in order to proceed.
🤔
I looked at `django-allauth` — it's using the `validate_email` instance,
in various, deeply-nested places — I think an issue over there, to look at
making that pluggable, is needed really. (In the meantime, one could
monkey patch `validate_email` with whatever validator you wanted to adjust
that… — again, not something I think we can just swap out from beneath
it.)
--
Ticket URL: <https://code.djangoproject.com/ticket/27029#comment:34>
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/0107018654235a87-7a51847f-2791-4522-81cb-31fd57779346-000000%40eu-central-1.amazonses.com.
