#26099: Migrations name conflict
-------------------------------+--------------------
Reporter: LucidComplex | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
Django's automatic migration creation may suffer from a name conflict
without any warning.
Creating a migration for a model having a relation with
"django.contrib.auth.models.User" will cause Django to automatically
import "django.conf.settings" in migrations.
This is all fine and good, unless you have an app unfortunately named
"settings". Django will not fire a warning about this name conflict.
--
Ticket URL: <https://code.djangoproject.com/ticket/26099>
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/055.af2a58d93a85e20da670ed0e054869f2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
