|
|
@@ -287,7 +287,7 @@ the :meth:`~BaseCommand.handle` method must be implemented.
|
|
|
|
|
|
Tries to execute this command, performing system checks if needed (as
|
|
|
controlled by the :attr:`requires_system_checks` attribute). If the command
|
|
|
- raises a :exc:`CommandError`, it's intercepted and printed to stderr.
|
|
|
+ raises a :exc:`CommandError`, it's intercepted and printed to ``stderr``.
|
|
|
|
|
|
.. admonition:: Calling a management command in your code
|
|
|
|
|
|
@@ -305,7 +305,8 @@ the :meth:`~BaseCommand.handle` method must be implemented.
|
|
|
|
|
|
Uses the system check framework to inspect the entire Django project for
|
|
|
potential problems. Serious problems are raised as a :exc:`CommandError`;
|
|
|
- warnings are output to stderr; minor notifications are output to stdout.
|
|
|
+ warnings are output to ``stderr``; minor notifications are output to
|
|
|
+ ``stdout``.
|
|
|
|
|
|
If ``app_configs`` and ``tags`` are both ``None``, all system checks are
|
|
|
performed. ``tags`` can be a list of check tags, like ``compatibility`` or
|
|
|
@@ -359,11 +360,11 @@ Exception class indicating a problem while executing a management command.
|
|
|
|
|
|
If this exception is raised during the execution of a management command from a
|
|
|
command line console, it will be caught and turned into a nicely-printed error
|
|
|
-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. It
|
|
|
-accepts the optional ``returncode`` argument to customize the exit status for
|
|
|
-the management command to exit with, using :func:`sys.exit`.
|
|
|
+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. It accepts the optional ``returncode`` argument to customize the exit
|
|
|
+status for the management command to exit with, using :func:`sys.exit`.
|
|
|
|
|
|
If a management command is called from code through
|
|
|
:func:`~django.core.management.call_command`, it's up to you to catch the
|
David