#24313: Deprecate the class_prepared signal --------------------------------------+------------------------------------ Reporter: aaugustin | Owner: nobody Type: Cleanup/optimization | Status: new Component: Core (Other) | Version: master 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 carljm):
* stage: Unreviewed => Accepted Comment: I agree. ISTM that since app-loading, Django shouldn't even need `class_prepared` internally anymore - but I realize there are dragons in that code. -- Ticket URL: <https://code.djangoproject.com/ticket/24313#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/067.d2802f44df1043a4e5a3b70cc5ffccbe%40djangoproject.com. For more options, visit https://groups.google.com/d/optout.