#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):
This does mean that, in the new world of required migrations, using
`AppConfig` to relabel third-party apps is pretty much impossible (due to
app-label being hardcoded in migration dependencies). So the idea that
`AppConfig.label` can allow using two third-party apps with conflicting
labels is dead (if those apps both have models/migrations).
--
Ticket URL: <https://code.djangoproject.com/ticket/23790#comment:9>
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.e7d4a47dc1368b1ffbbf166b855581cf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
