Hi everyone, I proceeded to revert the commit for now.
Nothing prevent us from adding a warning in the future if we ever fix the whole "blank" issue at the model level. Simon Le samedi 24 octobre 2015 12:29:44 UTC-4, Shai Berger a écrit : > > Hi, > > On Saturday 24 October 2015 04:13:47 charettes wrote: > > Hi everyone I'm the author of this change. > > > > I submitted a PR (https://github.com/django/django/pull/5471) to > completely > > revert this change given suggest adjustments don't get enough support. > > > I don't think that's the right fix. I think a field whose default value > fails > its "clean" method is bogus and should be flagged. A warning for sure, an > error > is not insensible. > > However, I'm very surprised to find out that a model field's "clean()" > method > even looks at the "blank" attribute. Like others on this thread, I was > under > the impression that it's only for model-form generation. > > 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/d5a29b88-4cb7-4d62-ab73-1fac46c41e2a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
