#18682: Make the deletion of stale content types safer
--------------------------------------+------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.contenttypes | Version: 1.3
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 timo):
I believe it's still relevant as the behavior is the same with migrations.
The only change is that the handler now uses the `post_migrate` signal
rather than `post_syncdb`.
--
Ticket URL: <https://code.djangoproject.com/ticket/18682#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.dc358ad7c9c57132cda0401783526c5a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
