#26099: Add a warning about import conflicts when auto-generating migrations
--------------------------------------+------------------------------------
Reporter: LucidComplex | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Migrations | Version: 1.8
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 Tim Graham):
There could be more import conflicts than just one for the name "settings"
so the approach should be more general. I'm not sure whether or not
solving this is feasible and/or practical.
--
Ticket URL: <https://code.djangoproject.com/ticket/26099#comment:8>
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/070.bf783ab08d66de39d5562f5ed1e4c153%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
