#33320: Inconsistencies around --no-input flags
-------------------------------------+-------------------------------------
Reporter: Peter Law | Owner: nobody
Type: Uncategorized | Status: closed
Component: Core (Management | Version: 3.2
commands) |
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
* ui_ux: 1 => 0
* component: Uncategorized => Core (Management commands)
* easy: 1 => 0
Comment:
> Some Django commands take a `--no-input` flag while others take a
`--noinput` flag. This means that rather than being able to just type a
spelling you've learned, you need to look it up for each command (or try
it and have it fail).
All built-in commands accept both `--noinput` and `--no-input` since
Django 1.9.
--
Ticket URL: <https://code.djangoproject.com/ticket/33320#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.3c9901be7f93f802c6f4228deb7fd212%40djangoproject.com.
