#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 Alexey Kotlyarov):
The needed parts of Django can be imported without `from`, so they stay
inside `django` namespace:
{{{
import django.conf.settings
import django.db.migrations
import django.db.models
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/26099#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.3860d914d2cd6525bd894c1439b6fe3d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
