mirror of
https://github.com/django/django.git
synced 2025-04-22 00:04:43 +00:00
[1.11.x] Made the @cached_property example more consistent.
Backport of 68f0bcb012fefffcf94b25dedd02c061a7544041 from master
This commit is contained in:
parent
fe51017efd
commit
93b53fb942
@ -477,16 +477,16 @@ https://web.archive.org/web/20110718035220/http://diveintomark.org/archives/2004
|
||||
{% for friend in person.friends %}
|
||||
|
||||
Here, ``friends()`` will be called twice. Since the instance ``person`` in
|
||||
the view and the template are the same, ``@cached_property`` can avoid
|
||||
that::
|
||||
the view and the template are the same, decorating the ``friends()`` method
|
||||
with ``@cached_property`` can avoid that::
|
||||
|
||||
from django.utils.functional import cached_property
|
||||
|
||||
@cached_property
|
||||
def friends(self):
|
||||
# expensive computation
|
||||
...
|
||||
return friends
|
||||
class Person(models.Model):
|
||||
|
||||
@cached_property
|
||||
def friends(self):
|
||||
...
|
||||
|
||||
Note that as the method is now a property, in Python code it will need to
|
||||
be invoked appropriately::
|
||||
|
Loading…
x
Reference in New Issue
Block a user