For what reason Zach? Without a canonical regex implementation to copy or include, we're stuck poorly reimplementing a bunch of esoteric rules to what end? The main purpose of email validation is to provide relevant feedback to the user, and to guard against obviously bad or malicious data. "Looks vaguely like an email address" is probably too loose to be useful, I admit. The proposal to copy the regex from the html5 email input widget seems like a fine compromise to me.
We should also err on the side of allowing incorrect addresses rather than rejecting correct addresses. I'd much rather have bad signups that need to be done again rather than users that can't sign up with their valid addresses. On Saturday, 2 April 2016 05:07:38 UTC+11, Zach Borboa wrote: > > -1 on less strict validation. Saying we need less strict validation > because emails are usually confirmed by sending an email to it, is akin to > saying urls are only valid if the url can be fetched. "Looks vaguely like a > url" would not be enough for validation purposes. I believe we should > strive to keep a reasonably strict and correct email validator. > -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1cc42853-f289-40a3-ac88-5ff3cfc26f04%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
