#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
--------------------------------------+------------------------------------
Changes (by Anton Samarchyan):
* cc: desecho@… (added)
Comment:
What if first it's going to check if there is an app called settings, then
if there is it's going to choose the name django_settings and check if the
app exists again (with the name django_settings), if it does, it's going
to name it django_settings_settings for example and check again, etc. Does
it sound good?
--
Ticket URL: <https://code.djangoproject.com/ticket/26099#comment:7>
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.d6da49b7f18fe349aa251128f51683b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
