#21175: abstract base model classes never fire class_prepared signal
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: cbabs
Type: Bug | Status: closed
Component: Database layer | Version: 1.5
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by carljm):
* status: assigned => closed
* resolution: => wontfix
Comment:
I am closing this; in light of #24313 and discussion on #24215, I no
longer think it makes sense for abstract models to fire `class_prepared`.
(In fact I'm hopeful that we can get rid of `class_prepared` altogether,
making it moot.)
--
Ticket URL: <https://code.djangoproject.com/ticket/21175#comment:5>
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/064.ac9f096235e8c8804ce7ffc841052abc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
