id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
34420	Migration import ordering violates coding style and isort defaults	Andy Chosak	Andy Chosak	"New migration files are generated with imports sorted by module, independent of import style. For example:

{{{#!python
import datetime
from django.db import migrations, models
import time
}}}

The [[https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/coding-style/#imports|Django coding style]] specifies:

  Place all {{{import}}} module statements before {{{from module import objects}}} in each section.

This guidance is the same as what isort does by default, [[https://pycqa.github.io/isort/docs/configuration/custom_sections_and_ordering.html#controlling-how-isort-sections-from-imports|as documented here]]. Newly generated migrations can fail isort for this reason.

This would mean migration files should instead be generated like this:

{{{#!python
import datetime
import time
from django.db import migrations, models
}}}

For reference, previous issues related to migration import sorting: #24155, #25384."	Cleanup/optimization	closed	Migrations	4.1	Normal	fixed	migrations		Ready for checkin	1	0	0	0	0	0