#27747: Add signals for Django management commands
-------------------------------------+-------------------------------------
Reporter: Dmitry Gladkov | Owner: nobody
Type: New feature | Status: new
Component: Core (Management | Version: master
commands) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Someday/Maybe
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* stage: Unreviewed => Someday/Maybe
Comment:
I'd like to see a consensus on the DevelopersMailingList before accepting
this feature. Adam already [https://groups.google.com/d/msg/django-
developers/JwYKEemPHFs/zC-Xe_ycBAAJ offered an opinion], "If there are
other use cases I think they'd also normally be better handled by more
specific signals, e.g. post_migrate, rather than a generic all-commands
signal." but this should be proposed on a separate thread.
--
Ticket URL: <https://code.djangoproject.com/ticket/27747#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 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/061.ca2515f87bf3c12b6b1f457cf05cb57b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
