[Django] #23447: Migrate management command doesn't follow documentation "Running management commands from your code"

[Django]

#23447: Migrate management command doesn't follow documentation "Running management
commands from your code"
--------------------------------------------+--------------------
Reporter: thenewguy | Owner: nobody
Type: Uncategorized | Status: new
Component: Core (Management commands) | Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------------+--------------------
According to the documentation at
https://docs.djangoproject.com/en/1.7/ref/django-admin/#running-
management-commands-from-your-code migrate can be called non-interactively
with call_command("migrate", noinput=True) but this doesn't work. It must
be run as call_command("migrate", interactive=False)

--
Ticket URL: <https://code.djangoproject.com/ticket/23447>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#23447: Migrate management command doesn't follow documentation "Running management
commands from your code"

-------------------------------------+-------------------------------------
Reporter: thenewguy | Owner: nobody
Type: Uncategorized | Status: closed
Component: Core (Management | Version: 1.7
commands) | Resolution:
Severity: Normal | worksforme
Keywords: | Triage Stage:
Has patch: 0 | Unreviewed
Needs tests: 0 | Needs documentation: 0
Easy pickings: 0 | Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):

* status: new => closed
* needs_better_patch: => 0
* resolution: => worksforme
* needs_tests: => 0
* needs_docs: => 0

Comment:

I'm not seeing where it's implied that the call_command option is
`noinput=True`. The example for flush is `management.call_command('flush',
verbosity=0, interactive=False)`.

Also, `call_command("migrate", noinput=True)` will work in Django 1.8 now
(see #22985) and I don't think it's worth adding additional documentation
for 1.7 since this issue has existed for a long time (although feel free
to reopen if you'd like to provide a patch).

--
Ticket URL: <https://code.djangoproject.com/ticket/23447#comment:1>