mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-10-24 06:06:09 +00:00
Code Issues 32 Releases Wiki Activity

Fixed #33842 -- Used :source: role for links to repo files on GitHub.

Browse Source
This commit is contained in:
Ramil Yanbulatov
2022-06-30 15:08:49 +03:00
committed by Carlton Gibson
parent f3a06b06b5
commit c6290bae9d
17 changed files with 28 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/howto/custom-model-fields.txt
View File

@@ -724,7 +724,7 @@ serialization formats. Here are a couple of tips to make things go more
smoothly:
#. Look at the existing Django fields (in
:file:`django/db/models/fields/__init__.py`) for inspiration. Try to find
:source:`django/db/models/fields/__init__.py`) for inspiration. Try to find
a field that's similar to what you want and extend it a little bit,
instead of creating an entirely new field from scratch.
@@ -761,7 +761,7 @@ In addition to the above details, there are a few guidelines which can greatly
improve the efficiency and readability of the field's code.
#. The source for Django's own ``ImageField`` (in
``django/db/models/fields/files.py``) is a great example of how to
:source:`django/db/models/fields/files.py`) is a great example of how to
subclass ``FileField`` to support a particular type of file, as it
incorporates all of the techniques described above.

4
docs/howto/custom-template-tags.txt
View File

@@ -1153,5 +1153,5 @@ The only new concept here is the ``self.nodelist.render(context)`` in
``UpperNode.render()``.
For more examples of complex rendering, see the source code of
:ttag:`{% for %}<for>` in ``django/template/defaulttags.py`` and
:ttag:`{% if %}<if>` in ``django/template/smartif.py``.
:ttag:`{% for %}<for>` in :source:`django/template/defaulttags.py` and
:ttag:`{% if %}<if>` in :source:`django/template/smartif.py`.

2
docs/howto/deployment/wsgi/modwsgi.txt
View File

@@ -197,7 +197,7 @@ admin app (and any other installed apps). This is however not the case when you
use any other server arrangement. You're responsible for setting up Apache, or
whichever web server you're using, to serve the admin files.
The admin files live in (:file:`django/contrib/admin/static/admin`) of the
The admin files live in (:source:`django/contrib/admin/static/admin`) of the
Django distribution.
We **strongly** recommend using :mod:`django.contrib.staticfiles` to handle the