Django doesn't depend on flake8, so it can't be used during migration
generation. Otherwise, I think aliasing the conflicting modules (6) is
indeed a better way.
The problem came about on #django IRC channel because someone named an app
"settings", presumably to store some configuration.
--
As stated in https://code.djangoproject.com/ticket/26099, it is possible
for a project with an unfortunately named application to result in a
migration file being generated which will raise an error on attempting to
migrate, without any prior warning. The problem is that the following
imports