id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
26597	Optparse incorrect relationship between `noinput` and `interactive` in management command	Joseph Kahn	nobody	"The option mapping for argparse in `call_command` is incorrectly mapping args. For example, it maps `noinput` to `interactive` and does not take into account that they are opposites. Here's where the bug is:

Because of the way options are parsed on:
https://github.com/django/django/blob/1.8.13/django/core/management/__init__.py#L106-L108

I assume this is present on other management commands, but I have not tested them.

(note, I simplified `opt_mapping` to just the example)
The following command:
`arg_options = {opt_mapping.get(key, key): value for key, value in options.items()}`
can be run as:
`{{'noinput': 'interactive'}.get(key, key): value for key, value in [('verbosity', 0), ('fake', True), ('list', True), ('fake_initial', True), ('app_label', 'tests'), ('noinput', True)]}`

leading to `interactive` being True."	Bug	closed	Migrations	1.8	Normal	needsinfo	migrate argparse command		Unreviewed	0	0	0	0	0	0