As Yo-Yo mentioned, there are valid use cases for blank=True, null=False, and I believe having one field option implicitly change another actually adds complexity instead of simplifying things.
On Monday, September 21, 2015 at 6:52:08 PM UTC-4, Paulo Maciel wrote: > > Why confused? It's optional, if the developer wanna put null=True, he > could. > I don't think need to be putting null = True, this is redundant. If this > is a standard behavior, you need not be explicit. > I think this should be optional, by default these fields should always be > null=True implicitly. > Django's philosophy is to simplify. > > Em quinta-feira, 17 de setembro de 2015 10:23:49 UTC-3, Tom Christie > escreveu: >> >> That kind of implicit behavior would just leave things more confused. >> Writing a few characters less code isn't a benefit if it comes at the >> expense of making the behavior less obvious. >> > -- 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/e6d1503d-1707-4715-8e15-c8cc268d372c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
