One additional note: has_changed is a lot more subtle than is_valid because it is used less often than is_valid (checked by grepping through our sources).
Am Donnerstag, 29. September 2016 17:18:35 UTC+2 schrieb Sven R. Kunze: > > That's works for me. > > Am Donnerstag, 29. September 2016 15:56:18 UTC+2 schrieb Tim Graham: >> >> Unless there are different arguments for has_changed vs. is_valid, I >> suggest we discuss both attributes on the nearly identical "is_valid as >> property" thread. >> >> On Thursday, September 29, 2016 at 9:40:38 AM UTC-4, Sven R. Kunze wrote: >>> >>> Good afternoon, >>> >>> I would like to follow up on >>> https://groups.google.com/forum/#!searchin/django-developers/is_authenticated$20as$20property%7Csort:relevance/django-developers/7k6Z8JxKH5Q/RoNKv66xcAMJ >>> >>> with regards to Form.has_changed. >>> >>> It's is not as security relevant as is_authenticated but the remaining >>> arguments of "is_authenticated as property" still hold. I also suggest the >>> usage of CallableBool as a good temporary backwards-compatibility measure. >>> >>> Best >>> Sven >>> >>> >>> NOTE: this one hid an especially annoying bug (also performance-wise) in >>> production for us. >>> >> -- 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/1153143c-e375-4d01-803d-9fabf2cf75c8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
