#29133: call_command() fails if a required option is passed in via **options
-------------------------------------+-------------------------------------
Reporter: Alex Tomic | Owner: Alex
Type: | Tomic
Cleanup/optimization | Status: assigned
Component: Core (Management | Version: 2.0
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* type: Uncategorized => Cleanup/optimization
Comment:
I'm not sure if the additional code complexity is worth supporting this. I
noted this recommendation from the Python documentation, "Required options
are generally considered bad form because users expect options to be
optional, and thus they should be avoided when possible." An alternative
could be to document the limitation.
--
Ticket URL: <https://code.djangoproject.com/ticket/29133#comment:2>
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/066.204c21615b78c928cdfcecb0c85f32c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
