This feature would create a management command, using itself a management
command.
--
Ticket URL: <https://code.djangoproject.com/ticket/29448>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* cc: Adam (Chainz) Johnson (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/29448#comment:1>
Comment (by Claude Paroz):
I'm not very thrilled by the idea. We already have detailed instructions
in the docs (https://docs.djangoproject.com/en/2.0/howto/custom-
management-commands/).
--
Ticket URL: <https://code.djangoproject.com/ticket/29448#comment:2>
* status: assigned => closed
* resolution: => wontfix
Comment:
I feel this one.
It's not that the instructions are good/correct, it's that "Ooo, I can
make a management command" leads straight to, "Oh, I have to create a
folder, and an `__init__.py`, Oh and another folder, Oh and another
`__init__.py`.
And then it's, "Oh, hang on, what are the imports?" and "What do I have to
subclass?" and "What methods do I need to implement?".
It's a real pain.
I'm going to say `wontfix` on this though, since [https://django-
extensions.readthedocs.io/en/latest/command_extensions.html Django
Extensions already implements a `create_command` command], which sets up
the folders and puts a command scaffolding in ([https://github.com/django-
extensions/django-
extensions/blob/master/django_extensions/conf/command_template/management/commands/sample.py.tmpl
that looks like this]).
That does the job perfectly. I don't think we can improve.
_Maybe_ pulling it into core, but the whole point of Django Extensions is
that useful stuff lives there that we haven't (and may or may not pull
in). As a community we should make sure users know it exists, since it's
great.
I hope that's fair. Katie, if you still think, "Yes, this should be in
core" then please follow up on Django Developers and we can discuss.
--
Ticket URL: <https://code.djangoproject.com/ticket/29448#comment:3>
Comment (by Katie McLaughlin):
Replying to [comment:3 Carlton Gibson]:
> I hope that's fair.
Totally fair.
> Django Extensions
I really need to investigate this one more. I was told in passing "Oh,
Django Extensions does that" (in the context of something else), but
without knowing what Django Extensions *is*, where it sits in the
ecosystem, and realising it's purpose, I totally accept that this issue is
outside of scope of core.
--
Ticket URL: <https://code.djangoproject.com/ticket/29448#comment:4>