#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: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* needs_better_patch: 0 => 1
Comment:
I'm not sure if that's a developer friendly change considering that
migrations can be authored and edited by hand. Defaulting to absolute
paths everywhere makes migration files more verbose and perhaps less
readable. I'd want a consensus on the DevelopersMailingList on this change
before proceeding.
--
Ticket URL: <https://code.djangoproject.com/ticket/26099#comment:13>
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.2a2a5efb34a5037abe7637fe5dfd09bb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
