On 29 Sep 2016, at 20:26, Sjoerd Job Postmus <sjoerd...@sjec.nl> wrote:
> Replacing functions with properties will create a lot of churn in the people > using the mentioned functions. > > Another approach might be to wrap these functions in a class with `__call__` > and `__bool__` both calling the underlying function. Or `__bool__` raising an > error? [1] That’s how the change was handled for is_authenticated/anonymous. However (IIRC) the plan is to only support property access after the deprecation completes. I’m afraid that supporting both styles in the long run would be confusing. -- Aymeric. -- 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/EF103864-1ED3-4B9A-83A6-57048BE8A35C%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
