From df1bb7ab2164ebc4e93b02befcf2c9b839d4c173 Mon Sep 17 00:00:00 2001 From: Jon Dufresne Date: Fri, 29 May 2020 12:09:57 -0700 Subject: [3.1.x] Changed some doc links to use intersphinx. Backport of 494ba27b5fe14e42e815edde6bd4a1216b29c935 from master --- docs/topics/db/queries.txt | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'docs/topics') diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt index ed69ae5762..2afd500e54 100644 --- a/docs/topics/db/queries.txt +++ b/docs/topics/db/queries.txt @@ -1315,8 +1315,9 @@ Using the models at the top of this page, for example, an ``Entry`` object ``e`` can get its associated ``Blog`` object by accessing the ``blog`` attribute: ``e.blog``. -(Behind the scenes, this functionality is implemented by Python descriptors_. -This shouldn't really matter to you, but we point it out here for the curious.) +(Behind the scenes, this functionality is implemented by Python +:doc:`descriptors `. This shouldn't really matter to +you, but we point it out here for the curious.) Django also creates API accessors for the "other" side of the relationship -- the link from the related model to the model that defines the relationship. @@ -1326,8 +1327,6 @@ For example, a ``Blog`` object ``b`` has access to a list of all related All examples in this section use the sample ``Blog``, ``Author`` and ``Entry`` models defined at the top of this page. -.. _descriptors: https://docs.python.org/howto/descriptor.html - One-to-many relationships ------------------------- -- cgit v1.3