Should migrations have their imports sorted?

Hello, some time ago, Django started to use isort to make sure imports are formatted and sorted consistently throughout the codebase. I like this very much, so I started adopting this practice for my own codebases. However, today I noticed that when Django generates a migration, the imports in

Re: Should migrations have their imports sorted?

I think it's been addressed in 1.9 to at least some extent. See https://github.com/django/django/commit/7f20041bca43ca33f0a9617793f2af7ab07c3fab On Saturday, July 25, 2015 at 6:54:40 PM UTC-4, Raphael Michel wrote: > > Hello, > > some time ago, Django started to use isort to make sure imports

Fellow Report - July 25, 2015

Report for week ending July 25, 2015: Triaged --- https://code.djangoproject.com/ticket/25146 - Allow method_decorator to work at the class level (accepted) https://code.djangoproject.com/ticket/25151 - rename LOGIN_REDIRECT_URL to POST_LOGIN_URL (won’t fix)