From e592574e6e3877eb9b5231e6630445e98a6e1841 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Tue, 10 Nov 2015 13:27:46 -0500 Subject: [PATCH] [1.8.x] Fixed #25727 -- Added a doc link to cached_property. Backport of e0de82c9b2c41c4c479d2245e7d5cd59638b5440 from master --- docs/topics/performance.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/topics/performance.txt b/docs/topics/performance.txt index 931d2d6fa4..718fa4762e 100644 --- a/docs/topics/performance.txt +++ b/docs/topics/performance.txt @@ -174,11 +174,11 @@ final steps towards producing well-performing code, not a shortcut. It's common to have to call a class instances's method more than once. If that function is expensive, then doing so can be wasteful. -Using the ``@cached_property`` decorator saves the value returned by a -property; the next time the function is called on that instance, it will return -the saved value rather than re-computing it. Note that this only works on -methods that take ``self`` as their only argument and that it changes the -method to a property. +Using the :class:`~django.utils.functional.cached_property` decorator saves the +value returned by a property; the next time the function is called on that +instance, it will return the saved value rather than re-computing it. Note that +this only works on methods that take ``self`` as their only argument and that +it changes the method to a property. Certain Django components also have their own caching functionality; these are discussed below in the sections related to those components.