#26099: Add a warning about import conflicts when auto-generating migrations
-------------------------------------+-------------------------------------
Reporter: LucidComplex | Owner: Alexey
Type: | Kotlyarov
Cleanup/optimization | Status: assigned
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):
While making changes, I found that the migration tests don't check the
imports inside the migration files properly, and it was possible for them
to pass even though the resulting migrations wouldn't have run on their
own:
https://github.com/django/django/commit/7bd4c3e75f3d9f9bbd43c2d4a39b786f2d75137d
I have a commit that fixes the imports, but I need to figure out how to
make a test for the bad application name.
--
Ticket URL: <https://code.djangoproject.com/ticket/26099#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/070.f109f720d183f6bc825eeeed1e633d39%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
