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
Style guide #65
Comments
I have no problem with undertaking either action. To me, black is something I wanted to try out. I see this project could be a good experimentation field for this. After all, it is widely used in other Python open-source projects. |
I'd add isort, but not |
Why? I never used |
I asked Andrew what he meant and he didn't mean to use |
After quick read in the black documentation, IMHO I think it'd be kind of redundant. The differences from fake8 is that black would suggest changes to follow the defined style and for me it would work super well in a private project where you can have an agreement with the developer to use black integrated with you editor. For a open source project I wouldn't mind to have different styles if it does not have any pep8 offence. Also if we are not using auto format, it's kind of annoying to check the diffs with the suggestions. |
We currently have flake8 in our linting command. We do not have isort in the project style guidelines.
Shall we add it?
Or try out something new like black?
The text was updated successfully, but these errors were encountered: