mirror of
https://github.com/django/django.git
synced 2025-07-20 01:29:11 +00:00
[1.9.x] Fixed #26294 -- Clarified call_command()'s handling of args and options.
Backport of 5695c142d282f4681a8d43bb55ec49f11f3fc40e from master
This commit is contained in:
parent
9ed08da6c6
commit
7b2ee75745
@ -1749,10 +1749,15 @@ To call a management command from code use ``call_command``.
|
|||||||
the name of the command to call.
|
the name of the command to call.
|
||||||
|
|
||||||
``*args``
|
``*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``
|
``**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::
|
Examples::
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user