Skip to content
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

Settle on python formatting/standard #294

Open
ThrowsException opened this issue May 11, 2020 · 2 comments
Open

Settle on python formatting/standard #294

ThrowsException opened this issue May 11, 2020 · 2 comments
Labels

Comments

@ThrowsException
Copy link
Collaborator

My vote is for black but there's also yapf and others. Something that is mostly pep8 preferred. We should come up with a formatting style and have PR's automatically format any committed code.

@FlipperPA
Copy link

I would highly recommend just going with black and forgetting about it. That's the direction the whole Python community is moving, and we've talked quite a bit about doing it for Django itself (though things move slowly there): https://groups.google.com/u/1/g/django-developers/c/wK2PzdGNOpQ/m/2RxsYsZhCQAJ

@MikeyManoguerra
Copy link
Collaborator

I would go with this choice as well. @ThrowsException mentioned doing this and the front end on #288 all as one commit that can be filtered out in git blame. That's honestly why I haven't done this yet, I really don't personally want to change every single line of the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants