#19737: Deprecate and then remove "shell" management command
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: | Status: new
Cleanup/optimization | Version: 1.4
Component: Core | Keywords:
(Management commands) | Has patch: 0
Severity: Normal | Needs tests: 0
Triage Stage: | Easy pickings: 0
Unreviewed |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
The only benefit of the "shell" management command is that it saves you
from having to set the DJANGO_SETTINGS_MODULE env var, and instead
automatically use the one set in ``manage.py``. This is a pretty minor
benefit; it's not hard to use your favorite technique (alias, script,
whatever) to reduce the number of characters you need to type to run
``DJANGO_SETTINGS_MODULE=someproj.settings python``, with the added
advantage that you can easily use any python REPL you like without having
to patch "shell" to explicitly support it.
The downside of having "shell" in Django is that it's a non-trivial
maintenance burden to decide which REPLs to support, add support for them,
and then update/fix that support through the years. We've already seen a
steady stream of tickets related to various edge-cases in IPython startup,
not to mention the major API changes in recent IPython versions. There's
no reason for Django to have to be maintaining code related to IPython.
--
Ticket URL: <https://code.djangoproject.com/ticket/19737>
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].
For more options, visit https://groups.google.com/groups/opt_out.
