#23790: Possible bad interaction between migration dependencies and relabeling
apps
-------------------------------+------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.7
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 carljm):
Last thought: using `AppConfig.label` for third-party apps with migrations
is still possible, I guess - you just have to use `MIGRATION_MODULES`
also, and regenerate all its migrations. Which gets unfortunate if the app
is upgraded and ships a new migration; you'd have to always re-create
those yourself.
--
Ticket URL: <https://code.djangoproject.com/ticket/23790#comment:11>
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.b378202ca94825ca54aae378c515a3ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
