Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[1.11.x] Made the @cached_property example more consistent.

Browse Source 
Backport of 68f0bcb012fefffcf94b25dedd02c061a7544041 from master
This commit is contained in:
Bryan Helmig 2017-08-10 11:54:19 -04:00 committed by Tim Graham
parent fe51017efd
commit 93b53fb942
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/ref/utils.txt
View File

@ -477,16 +477,16 @@ https://web.archive.org/web/20110718035220/http://diveintomark.org/archives/2004
{% for friend in person.friends %} {% for friend in person.friends %}
Here, ``friends()`` will be called twice. Since the instance ``person`` in Here, ``friends()`` will be called twice. Since the instance ``person`` in
the view and the template are the same, ``@cached_property`` can avoid the view and the template are the same, decorating the ``friends()`` method
that:: with ``@cached_property`` can avoid that::
from django.utils.functional import cached_property from django.utils.functional import cached_property
@cached_property class Person(models.Model):
def friends(self):
# expensive computation @cached_property
... def friends(self):
return friends ...
Note that as the method is now a property, in Python code it will need to Note that as the method is now a property, in Python code it will need to
be invoked appropriately:: be invoked appropriately::