#28367: Document how to override management commands
--------------------------------------+------------------------------------
Reporter: stephanm | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham):
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
* component: Uncategorized => Documentation
Comment:
You need to use unique command names -- there's no notion of namespacing,
though this was suggested in #27189, I don't think there was an follow up
on that idea.
I'll classify this as a documentation ticket for explaining how to
override management commands. There's a brief discussion
[https://stackoverflow.com/questions/29320103/if-multiple-django-apps-
define-the-same-custom-management-command-which-is-used on StackOverflow]
which could be a useful starting point in writing some docs.
--
Ticket URL: <https://code.djangoproject.com/ticket/28367#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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.69b93f51747fd471fafdc19e13495245%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
