Misleading list of options available for manage.py commands
Every commands has some options available, since the BaseCommand
initialize some options to the options parser: verbosity, settings, traceback..
However, this can be misleading, because these arguments are not used by every commands and sometimes this choice is by design. For example, the runserver
command does not use the verbosity
option, and it has been explained why only there: https://code.djangoproject.com/ticket/15132
I think the framework should not show generic options that are not used in the current commands (through an explicit list of generic options ignored or an explicit list of commands used ?)
Summary: |
Misleading → Misleading list of options available for manage.py commands
|
Triage Stage: |
Unreviewed → Accepted
|
Type: |
Bug → Cleanup/optimization
|
Owner: |
changed from nobody to Edald123
|
Status: |
new → assigned
|
Owner: |
Edald123 removed
|
Status: |
assigned → new
|
Owner: |
set to Yuneui Jeong
|
Status: |
new → assigned
|
Patch needs improvement: |
set
|
Has patch: |
unset
|
Patch needs improvement: |
unset
|
Owner: |
Yuneui Jeong removed
|
Status: |
assigned → new
|
Owner: |
set to Jan Szoja
|
Status: |
new → assigned
|
Cc: |
Jan Szoja added
|
Has patch: |
set
|
Needs tests: |
set
|
Patch needs improvement: |
set
|
Needs documentation: |
unset
|
Needs tests: |
unset
|
Patch needs improvement: |
unset
|
Easy pickings: |
unset
|
Triage Stage: |
Accepted → Ready for checkin
|
Resolution: |
→ fixed
|
Status: |
assigned → closed
|
I don't know that this is a big problem that is worth changing, but I guess if someone wants to propose a patch to fix the issue for
runserver
, we could entertain it. The documentation says these options are "available on all options" so this would require an update too. One consideration is that subclasses ofrunserver
might use these options (verbosity
most likely) so removing them by default would be backwards incompatible.