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?
On Saturday, March 26, 2016 at 5:25:04 AM UTC-4, Shai Berger wrote: > > On Tuesday 15 March 2016 04:51:50 Markus Holtermann wrote: > > > > > WRT the backwards compatibility issues: > > > > 2) You're not able to submit an email address that does not pass the new > > validator but the old one. --> Unlikely, but when the new field is of > > type="email" your rather modern browser will tell you before Django > > anyway > > > > While this is correct, in many of your rather modern web applications > Django > does not own the front-end, and for web services, a relevant front end > doesn't > even necessarily exist. > > So the backward-incompatibility is not horrible, but it exists and needs > to be > mitigated by a deprecation cycle. > > 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 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/4f821407-4ebb-47ec-9a78-d17b3cf5014a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
