#25931: ContentTypes population doesn't work with backwards migrations
--------------------------------------+------------------------------------
Reporter: amosonn | Owner: nobody
Type: Bug | Status: new
Component: contrib.contenttypes | Version: 1.9
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
--------------------------------------+------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0
* stage: Unreviewed => Accepted
Comment:
This is related to #24100 and the tickets mentioned there, and also #24865
which suggests removing content type deletion from the `post_migrate()`
signal which should make things a bit safer. I'll accept this ticket,
though I'm not sure what exactly the remaining work will be (if any) after
those other tickets are resolved.
--
Ticket URL: <https://code.djangoproject.com/ticket/25931#comment:1>
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/065.40a39e81c3a90775ddbf44d318d6be33%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
