We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is an individual case that relates to #694
note: I found this earlier this week before 5.0 release but just confirmed it on 5.0.2 (p.s. congrats on the new release)
Black version: ❯ black --version black, version 19.10b0 Isort Version: ❯ pip list | grep isort isort 5.0.2 (version displayed this way due to #1255 )
❯ black --version black, version 19.10b0
❯ pip list | grep isort
isort 5.0.2
default settings for both tools
import os import random import certifi # don't import fantasticFlake until they release it # import fantasticFlake import flake8 import isort
Personally I think Isort's format is better/more correct but that decision I leave to the authors of these awesome tools.
The text was updated successfully, but these errors were encountered:
Oh it looks like this was brought up in psf/black#251
and the fix is to set ensure_newline_before_comments which makes isort behave like black. Closing this out.
ensure_newline_before_comments
or just use the new feature profiles with the black option https://timothycrosley.github.io/isort/docs/configuration/profiles/
Sorry, something went wrong.
No branches or pull requests
This is an individual case that relates to #694
note: I found this earlier this week before 5.0 release but just confirmed it on 5.0.2 (p.s. congrats on the new release)
Black version:
❯ black --version black, version 19.10b0
Isort Version:
❯ pip list | grep isort
isort 5.0.2
(version displayed this way due to #1255 )
default settings for both tools
Isort's Desired Format
Black's Desired Format
Personally I think Isort's format is better/more correct but that decision I leave to the authors of these awesome tools.
The text was updated successfully, but these errors were encountered: