From c8d21f335113dcf6009d7aa9810d4e77dc58c75d Mon Sep 17 00:00:00 2001 From: Andrew Nester Date: Sat, 28 Jan 2017 00:12:45 +0300 Subject: [PATCH] Fixed #27769 -- Documented option naming differences between django-admin and call_command(). --- docs/ref/django-admin.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/ref/django-admin.txt b/docs/ref/django-admin.txt index 6a36f77310..ea025559e9 100644 --- a/docs/ref/django-admin.txt +++ b/docs/ref/django-admin.txt @@ -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'])