#24865: Add a feature to programmatically remove stale content types
--------------------------------------+------------------------------------
Reporter: Protosac | Owner: nobody
Type: New feature | Status: new
Component: contrib.contenttypes | Version: master
Severity: Normal | Resolution:
Keywords: stale contenttypes | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by timgraham):
Markus and I chatted in IRC and came up with the idea of moving stale
content types deletion out of the `post_migrate` signal
`update_contenttypes` function and into a separate
`remove_stale_contenttypes` management command. This would default to
`interactive=True` but could be called with
`call_command('remove_stale_contenttypes', interactive=False)` to delete
without a prompt.
How does this sound?
--
Ticket URL: <https://code.djangoproject.com/ticket/24865#comment:13>
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/066.030254b8a309af203ca92e3bf2505b01%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
