diff options
| author | Jon Dufresne <jon.dufresne@gmail.com> | 2020-05-29 12:09:57 -0700 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2020-05-29 21:10:34 +0200 |
| commit | df1bb7ab2164ebc4e93b02befcf2c9b839d4c173 (patch) | |
| tree | dce2474d41a038a3d08b8a8b660f68c43f0b67a4 | |
| parent | aca675ad33c1673a464172182bc66d8cd16efaa5 (diff) | |
[3.1.x] Changed some doc links to use intersphinx.
Backport of 494ba27b5fe14e42e815edde6bd4a1216b29c935 from master
| -rw-r--r-- | docs/howto/windows.txt | 6 | ||||
| -rw-r--r-- | docs/topics/db/queries.txt | 7 |
2 files changed, 5 insertions, 8 deletions
diff --git a/docs/howto/windows.txt b/docs/howto/windows.txt index 9d67bd9e5e..fecdbf3fba 100644 --- a/docs/howto/windows.txt +++ b/docs/howto/windows.txt @@ -57,8 +57,8 @@ It is best practice to provide a dedicated environment for each Django project you create. There are many options to manage environments and packages within the Python ecosystem, some of which are recommended in the `Python documentation <https://packaging.python.org/guides/tool-recommendations/>`_. -Python itself comes with `venv`_ for managing environments which we will use -for this guide. +Python itself comes with :doc:`venv <python:tutorial/venv>` for managing +environments which we will use for this guide. To create a virtual environment for your project, open a new command prompt, navigate to the folder where you want to create your project and then enter the @@ -75,8 +75,6 @@ The virtual environment will be activated and you'll see "(project-name)" next to the command prompt to designate that. Each time you start a new command prompt, you'll need to activate the environment again. -.. _venv: https://docs.python.org/3/tutorial/venv.html - Install Django ============== 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 <python:howto/descriptor>`. 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 ------------------------- |