Changed some doc links to use intersphinx.
This commit is contained in:
parent
f8ef5f2c86
commit
494ba27b5f
|
@ -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
|
you create. There are many options to manage environments and packages within
|
||||||
the Python ecosystem, some of which are recommended in the `Python
|
the Python ecosystem, some of which are recommended in the `Python
|
||||||
documentation <https://packaging.python.org/guides/tool-recommendations/>`_.
|
documentation <https://packaging.python.org/guides/tool-recommendations/>`_.
|
||||||
Python itself comes with `venv`_ for managing environments which we will use
|
Python itself comes with :doc:`venv <python:tutorial/venv>` for managing
|
||||||
for this guide.
|
environments which we will use for this guide.
|
||||||
|
|
||||||
To create a virtual environment for your project, open a new command prompt,
|
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
|
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
|
to the command prompt to designate that. Each time you start a new command
|
||||||
prompt, you'll need to activate the environment again.
|
prompt, you'll need to activate the environment again.
|
||||||
|
|
||||||
.. _venv: https://docs.python.org/3/tutorial/venv.html
|
|
||||||
|
|
||||||
Install Django
|
Install Django
|
||||||
==============
|
==============
|
||||||
|
|
||||||
|
|
|
@ -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:
|
can get its associated ``Blog`` object by accessing the ``blog`` attribute:
|
||||||
``e.blog``.
|
``e.blog``.
|
||||||
|
|
||||||
(Behind the scenes, this functionality is implemented by Python descriptors_.
|
(Behind the scenes, this functionality is implemented by Python
|
||||||
This shouldn't really matter to you, but we point it out here for the curious.)
|
: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 --
|
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.
|
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``
|
All examples in this section use the sample ``Blog``, ``Author`` and ``Entry``
|
||||||
models defined at the top of this page.
|
models defined at the top of this page.
|
||||||
|
|
||||||
.. _descriptors: https://docs.python.org/howto/descriptor.html
|
|
||||||
|
|
||||||
One-to-many relationships
|
One-to-many relationships
|
||||||
-------------------------
|
-------------------------
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue