Having a new field seems overkill to me -- a new validation routine which is less strict is something we should be able to do without backward compat considerations. The reasoning for this is easy: As long as it is not proven that the current regex covers only valid addresses a less strict validation is not harming anyone. Especially since even if an email address is technically valid, it does not mean that is actually exists -- so you will have to send an email to verify the address anyways…
On Thursday, March 31, 2016 at 12:53:25 AM UTC+2, Shai Berger wrote: > > On Wednesday 30 March 2016 15:45:23 Tim Graham wrote: > > How did you imagine the deprecation cycle working? Do you want Django to > > raise a warning saying that the regular expression is changing and > provide > > a temporary setting or something to opt-in to the simpler validation? > > > > Yes, that's one option; another is to define a HTML5EmailField (or a > better > name) that uses the simpler validation, and warn that EmailField is going > to > turn into an alias of that -- so that each EmailField in the project is > handled separately. > > Also, I'm not sure it's possible to have the warning produced by a check; > but > if it is, that would be preferable. > > Shai. > -- 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 https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1ac1f8f4-71a2-4867-9306-9d9522496810%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
