p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Fixed #26294 -- Clarified call_command()'s handling of args and options.

This commit is contained in:
Tim Graham 2016-03-12 17:44:08 -05:00
parent 402da9ab7b
commit 5695c142d2
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/ref/django-admin.txt
View File

@ -1764,10 +1764,15 @@ To call a management command from code use ``call_command``.
preferred unless the object is required for testing.
``*args``
a list of arguments accepted by the command.
a list of arguments accepted by the command. Arguments are passed to the
argument parser, so you can use the same style as you would on the command
line. For example, ``call_command('flush', 'verbosity=0')``.
``**options``
named options accepted on the command-line.
named options accepted on the command-line. Options are passed to the command
without triggering the argument parser, which means you'll need to pass the
correct type. For example, ``call_command('flush', verbosity=0)`` (zero must
be an integer rather than a string).
Examples::