You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Changing the ordering in the fixers appears to fix the issue, but I'm wondering if this is somehow intentional or there's another reason for this, given the docstring comments on the fixers showing the imports in the correct order.
If this is a bug, and it is agreed they should be in alphabetical order, I can put up a PR to fix it.
The text was updated successfully, but these errors were encountered:
ascandella
added a commit
to ascandella/python-future
that referenced
this issue
Apr 3, 2019
These appear to be backwards from the recommended (isort/alphabetical) order:
Changing the ordering in the fixers appears to fix the issue, but I'm wondering if this is somehow intentional or there's another reason for this, given the docstring comments on the fixers showing the imports in the correct order.
If this is a bug, and it is agreed they should be in alphabetical order, I can put up a PR to fix it.
The text was updated successfully, but these errors were encountered: