summaryrefslogtreecommitdiff
path: root/docs/howto
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2016-01-12 18:01:29 -0500
committerTim Graham <timograham@gmail.com>2016-01-12 18:01:29 -0500
commita7752780d9e78e12d0bd7bd2dcf920d304e039bc (patch)
tree435e3e06a373de803e78e681a5880d957d51ded3 /docs/howto
parent555f8e9d5c640373d2bd30ec1212b341c859f828 (diff)
Removed an unncessary docs cross-reference for call_command().
Diffstat (limited to 'docs/howto')
-rw-r--r--docs/howto/custom-management-commands.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/howto/custom-management-commands.txt b/docs/howto/custom-management-commands.txt
index 0b71f1ef8b..9e338a4bdf 100644
--- a/docs/howto/custom-management-commands.txt
+++ b/docs/howto/custom-management-commands.txt
@@ -309,7 +309,7 @@ the :meth:`~BaseCommand.handle` method must be implemented.
.. admonition:: Calling a management command in your code
``execute()`` should not be called directly from your code to execute a
- command. Use :ref:`call_command <call-command>` instead.
+ command. Use :func:`~django.core.management.call_command` instead.
.. method:: BaseCommand.handle(*args, **options)
@@ -374,5 +374,6 @@ message to the appropriate output stream (i.e., stderr); as a result, raising
this exception (with a sensible description of the error) is the preferred way
to indicate that something has gone wrong in the execution of a command.
-If a management command is called from code through :ref:`call_command
-<call-command>`, it's up to you to catch the exception when needed.
+If a management command is called from code through
+:func:`~django.core.management.call_command`, it's up to you to catch the
+exception when needed.