-
Notifications
You must be signed in to change notification settings - Fork 44
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
Common Python formatting #81
Comments
there's already also, why you're getting merge conflicts when doing small changes?! are you sure your |
The good news is that I've done most (all?) the things I want so there will be less change Maybe we should add a black config file as @tomato42 set the line length to 79 which is non-standard |
I'm not sure where we are with this, but I think it can be closed unless you have concerns @jpgoldberg |
+1 for closing |
I am finding myself in a sea of merge conflicts even when I think I am making a minor change., I suspect that some of this is due to me (tacitly) using a different fill formatting convention and getting loads of whitespace. That is, I am seeing diffs reported where I do not need a difference.
I would like to recommend that we settle on a common python formatting and linting system. Personally, I would prefer using ruff and we create a
ruff.toml
file for any non-default settings and for settling on a line length. But I will go along with what others prefer, as long as we settle on something.The text was updated successfully, but these errors were encountered: