-
Notifications
You must be signed in to change notification settings - Fork 271
Run black on all files #1325
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
Run black on all files #1325
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, could you add the specific command to run black to this page of the docs please: https://axelrod.readthedocs.io/en/stable/tutorials/contributing/guidelines.html
(The format of bullet point 3 is a bit weird if you could fix that while you're there.)
I didn't think there would be so many changes to so many files, do you mind holding off until after I finish #1288 ? I'm assuming that you would just have to run black again and that wouldn't create much extra effort. |
@marcharper That's fine with me. |
I was surprised when you suggested it would be fine :) 👍 |
all code and the `isort utility <https://github.com/timothycrosley/isort>`_ to | ||
sort import statements. You can run black on all code with:: | ||
|
||
$ python -m black -l 80 . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this TJ 👍
Closing in favor of #1368 |
Fixes #1312
First commit runs black on all files. Second commit adds a check to config.yml.
I didn't make any changes to the contribution docs, because they already say that you should run black on all files.