Re: [Django] #27747: Add signals for Django management commands
#27747: Add signals for Django management commands -+- Reporter: Dmitry Gladkov |Owner: nobody Type: New feature | Status: new Component: Core (Management | Version: dev 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 Ülgen Sarıkavak): * cc: Ülgen Sarıkavak (added) -- Ticket URL: <https://code.djangoproject.com/ticket/27747#comment:4> 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/0107018e50583e1b-4d66c9ed-9bac-47a5-9731-95389c294c99-00%40eu-central-1.amazonses.com.
Re: [Django] #27747: Add signals for Django management commands
#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 -+- Comment (by Carlton Gibson): For runserver, in particular, I'm suspecting that, at this late stage, they'll be some kind of rewrite making it async, to use presumably asyncio. The autoreloader in the particular seems to be crying out for this... As such, I'd suggesting adding functionality as part of that to control subprocesses (or whatever else) rather than using signals. -- Ticket URL: <https://code.djangoproject.com/ticket/27747#comment:3> 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 view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/061.06e81e0ddd2313a908d48070fb6f2ec8%40djangoproject.com.
Re: [Django] #27747: Add signals for Django management commands
#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 -+- Comment (by Matthew Schinckel): The one I have in mind is being able to fire off a seperate process when starting `runserver` (for instance, to make sure that our JS build pathway stuff has a "watch" server running). -- Ticket URL: <https://code.djangoproject.com/ticket/27747#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 view this discussion on the web visit https://groups.google.com/d/msgid/django-updates/061.b0ca2b4974465a102c282820ee2bbd7d%40djangoproject.com.
Re: [Django] #27747: Add signals for Django management commands
#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.
[Django] #27747: Add signals for Django management commands
#27747: Add signals for Django management commands -+- Reporter: Dmitry | Owner: nobody Gladkov| Type: New| Status: new feature| Component: Core |Version: master (Management commands) | Severity: Normal | Keywords: Triage Stage: | Has patch: 0 Unreviewed | Needs documentation: 0 |Needs tests: 0 Patch needs improvement: 0 | Easy pickings: 0 UI/UX: 0 | -+- Related PR: https://github.com/django/django/pull/7857 Suggested example usage (I know that a string can't be a signal sender, this is just for illustrating the point): {{{#!python from django.core.management import signals def handle_pre(sender, instance): instance.stdout.write('Hello World') def handle_post(sender, instance): instance.stdout.write('Bye World') signals.pre_command.connect(handle_pre, sender='runserver') signals.post_command.connect(handle_post, sender='runsever') }}} Reasoning: Currently overriding of commands in Django can only be achieved by shadowing existing commands using `INSTALLED_APPS` initialization order. This is a perfectly good solution if a user needs to completely override a command, but it's not ideal for extending/adding functionality to existing commands. Extending the same command from different apps will not work as only the extended command from the latest `INSTALLED_APPS` entry will run (see Example 2). Some examples of actions that can be achieved using singals: 1. Pulling remote translations before `compilemessages`. 2. Showing coverage or/and generating xml report after `test`. 3. Running optipng on collected static images after `collectstatic` 4. Displaying useful information like outdated package versions before `runserver`. -- Ticket URL: <https://code.djangoproject.com/ticket/27747> 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/046.36b28dd3aed61c03394956a205d61cd5%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.