#24313: Deprecate the class_prepared signal
--------------------------------------+------------------------------------
Reporter: Aymeric Augustin | Owner: (none)
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 Gurpreet Singh):
* owner: Gurpreet Singh => (none)
* status: assigned => new
Comment:
Replying to [comment:8 Alex Hill]:
> Alright, there is at least one gap in functionality: using
`class_prepared`, you can fiddle with models in ways that propagate to
their subclasses. In `AppConfig.ready()`, since all the `ModelBase`
inheritance magic has already happened, it's too late to do anything like
that.
I shouldn't have chosen to work on this as my first ticket then it seems.
--
Ticket URL: <https://code.djangoproject.com/ticket/24313#comment:10>
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.f3c02bd2c8e3583773d4a2d9723537bc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
