-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
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
black not producing flake8 compatible code #113
Comments
I think this is because since #21 a linebreak is introduced before a binary operator to conform to PEP8. I would ignore I'll defer to someone else for |
For "line too long", just add organizing parentheses to your assignment and it will do the correct thing. Next version is going to do that automatically. Yeah, disable W503, it's wrong. |
Sounds like this is mostly me misunderstanding the expected state. Thanks for the replies. |
They disagree with black, and the Internet says that Black is right. psf/black#113 psf/black#315
Have to ignore flake8 E203 and W503 - they disagree with black, and the Internet says that black is right. psf/black#113 psf/black#315
Have to ignore flake8 E203 and W503 - they disagree with black, and the Internet says that black is right. psf/black#113 psf/black#315
Howdy! Sorry you're having trouble. To expedite your experience,
provide some basics for me:
Operating system: Linux
Python version: 3.6.3
Black version: 18.4a0
Does also happen on master: yes
I've run black on a codebase that is already flake8 compatible, and it ends up reformatting things in such a way that it fails a whole bunch of flake8 checks. For example:
One of the diffs that seems to be causing some of the issues is:
(And many more - it looks like around ~150 total flake8 failures).
This can be reproduced locally by cloning https://github.com/mozilla/balrog, changing tox.ini's max-line-length to 120 (I'm planning to change the line length at the same time as reformatting with Black), and running flake8 before & after running black.
The text was updated successfully, but these errors were encountered: