#24313: Deprecate the class_prepared signal
--------------------------------------+------------------------------------
Reporter: Aymeric Augustin | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Core (Other) | Version: dev
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 Michael Manfre):
Another use case for `class_prepared` is allowing an abstract Model to
define indexes that 1) require a name (e.g. has conditions) where the
inheriting class name is too long for the index 30 character limit, or 2)
should be inherited even if the subclass defines its own indexes.
--
Ticket URL: <https://code.djangoproject.com/ticket/24313#comment:9>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701856e711319-6ccddabb-a57d-443b-b93e-2e18fae87922-000000%40eu-central-1.amazonses.com.
