#26640: class_prepared is not a ModelSignal and differs from documentation
-------------------------------------+-------------------------------------
Reporter: AlexHill | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by AlexHill):
I've added some comments in that ticket. I think deprecating the signal is
probably a good idea.
Would deprecating the `class_prepared` and fixing the issues in this
ticket be mutually exclusive?
--
Ticket URL: <https://code.djangoproject.com/ticket/26640#comment:3>
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/066.3fbabdb86f5549cc71e48567ddfa5371%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
