Am Donnerstag, 29. September 2016 15:52:00 UTC+2 schrieb Tim Graham: > > I don't think the same argument applies because no one (I hope) is calling > form.is_valid() in templates. >
Could you elaborate why this only plays a role with templates? So, as it turns out I ran grep on our code and easily found a place where the programmer missed the "()" after is_valid. Regarding templates, I found no occurrences of "is_valid" nor "has_changed" in our templates so far but this might have other reasons as we don't have a very long history of templates until recently. Additionally, what's so wrong about using either function in templates? -- 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/74aee2cb-66d7-466a-8a79-c0e25d91a95e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
