p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #27769 -- Documented option naming differences between django-admin and call_command().

This commit is contained in:
Andrew Nester 2017-01-28 00:12:45 +03:00 committed by Tim Graham
parent 56ea394dfd
commit c8d21f3351
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1776,6 +1776,13 @@ Named arguments can be passed by using either one of the following syntaxes::
# `use_natural_foreign_keys` is the option destination variable
management.call_command('dumpdata', use_natural_foreign_keys=True)
Some command options have different names when using ``call_command()`` instead
of ``django-admin`` or ``manage.py``. For example, ``django-admin
createsuperuser --no-input`` translates to ``call_command('createsuperuser',
interactive=False)``. To find what keyword argument name to use for
``call_command()``, check the command's source code for the ``dest`` argument
passed to ``parser.add_argument()``.
Command options which take multiple options are passed a list::
management.call_command('dumpdata', exclude=['contenttypes', 'auth'])