#29301: Reorder management command arguments in --help output to prioritize
command-specific arguments
-------------------------------------+-------------------------------------
Reporter: David Foster | Owner: David
Type: | Foster
Cleanup/optimization | Status: closed
Component: Core (Management | Version: 2.0
commands) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jann Haber):
I have an observation on the change made above:
If any third-party app now adds one of the default arguments in the
.add_argument() function, django now fails trying to re-add the argument.
What would be the desired outcome in case of a conflict?
As an example:
django_nose adds a --version argument (showing the nose version). It
checks, if there is already a --version argument installed and if not,
adds the argument to the parser. In Django 2.0.5, it found the --version
argument from django and did nothing. In Django 2.1a1, it adds the
--version argument to the parser. Later, Django 2.1a1 fails trying to add
another --version argument.
--
Ticket URL: <https://code.djangoproject.com/ticket/29301#comment:6>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.f2a26dcae4dc5984921a4e8cf4e3e45b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
