#25384: New Migrations Generated with Improperly Sorted Imports
--------------------------------------+------------------------------------
Reporter: jambonrose | 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: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by MarkusH):
* status: closed => new
* resolution: duplicate =>
* stage: Unreviewed => Accepted
Comment:
As briefly discussed on IRC the other day, I add a patch for 1.8 to change
the order of those two imports. It's annoying to change the order
manually.
The issue is indeed fixed on master.
--
Ticket URL: <https://code.djangoproject.com/ticket/25384#comment:6>
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/068.bc6f94e6e8645d1e9221119823579fe2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
