mirror of
https://github.com/django/django.git
synced 2025-08-03 10:34:04 +00:00
Corrected multiply defined labels in docs.
This commit is contained in:
parent
95a4db3fbd
commit
60503cc747
3 changed files with 27 additions and 24 deletions
|
@ -87,15 +87,13 @@ function or method::
|
|||
Notice that the function takes a ``sender`` argument, along with wildcard
|
||||
keyword arguments (``**kwargs``); all signal handlers must take these arguments.
|
||||
|
||||
We'll look at senders `a bit later`_, but right now look at the ``**kwargs``
|
||||
argument. All signals send keyword arguments, and may change those keyword
|
||||
arguments at any time. In the case of
|
||||
We'll look at senders :ref:`a bit later <connecting-to-specific-signals>`, but
|
||||
right now look at the ``**kwargs`` argument. All signals send keyword
|
||||
arguments, and may change those keyword arguments at any time. In the case of
|
||||
:data:`~django.core.signals.request_finished`, it's documented as sending no
|
||||
arguments, which means we might be tempted to write our signal handling as
|
||||
``my_callback(sender)``.
|
||||
|
||||
.. _a bit later: `connecting to signals sent by specific senders`_
|
||||
|
||||
This would be wrong -- in fact, Django will throw an error if you do so. That's
|
||||
because at any point arguments could get added to the signal and your receiver
|
||||
must be able to handle those new arguments.
|
||||
|
|
|
@ -261,11 +261,11 @@ backend with different options. In that case you should define a unique
|
|||
|
||||
:setting:`OPTIONS <TEMPLATES-OPTIONS>` contains backend-specific settings.
|
||||
|
||||
.. _template-loading:
|
||||
|
||||
Usage
|
||||
-----
|
||||
|
||||
.. _template-loading:
|
||||
|
||||
.. module:: django.template.loader
|
||||
|
||||
The ``django.template.loader`` module defines two functions to load templates.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue