#24313: Deprecate the class_prepared signal
------------------------------------------------+------------------------
Reporter: aaugustin | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Since 1.7, whatever can be done in a `class_prepared` listener is probably
better done by inspecting the app registry in `AppConfig.ready()`.
As the documentation notes, reacting to `class_prepared` is impractical
because the app-loading and meta-refactor APIs don't work yet.
Even if we keep the signal — I once tried to refactor this area and it
[https://code.djangoproject.com/ticket/21719#comment:13 went downhill
quickly] — I think we should remove it from the public API.
--
Ticket URL: <https://code.djangoproject.com/ticket/24313>
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.9d57d351819f62ddfac2bf69fd393b69%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
