#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
--------------------------------------+------------------------------------
Comment (by AlexHill):
Replying to [comment:2 carljm]:
> For reference, the only place Django internally uses `class_prepared` is
to call `do_pending_lookups` to handle unresolved relations to the just-
loaded model. It certainly seems that could/should be handled by the app
registry instead...
Hi Carl, I've opened ticket #24215 and
[https://github.com/django/django/pull/3984/files written a patch] to do
just this - feedback welcome.
--
Ticket URL: <https://code.djangoproject.com/ticket/24313#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 [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/067.2025c27f28c0c22375600db0850baf71%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
