I’m slightly skeptical - a cached class property seems slightly iffy and could be achieved with just a @functools.cache’d classmethod instead?
Is there a specific use case where a cached, class _property_ would be the best way? And perhaps we need to care about concurrent access here, more than with our other cache implementations. However, this is a really small change, so maybe it’s OK. Tom > On 30 Dec 2020, at 14:46, Boris Krause <mgbit3...@gmail.com> wrote: > Hello, > I propose new feature - decorator cached_classproperty. > Django has a lot of methods for caching, like cached_page and cached_property. > Сaching improves response times. > For me it was useful. > What do you think about it? > https://github.com/django/django/pull/13813 > Thanks!:) > -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/fe13f5c9-8ef5-44eb-bfc4-731865a9123an%40googlegroups.com. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4E510911-08BE-4B94-8BD8-97B8391709C0%40tomforb.es.
