-
Notifications
You must be signed in to change notification settings - Fork 75
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
Apply general spring style formatting 🌻 #860
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.
I'm 👍 on adding bugbear and following its recommendations, 👎 on "general formatting changes" which make this a very noisy PR (lots of conflict management to be expected with other long-running branches) and contain changes not mandated by our official linting checks.
Hi @Morendil !
I'll split in two different pull requests.
What could we do to solve that issue? Split in several different pull requests? Or maybe it is just not worth the effort and we should live with it.
I did a catch-all to go fast so there maybe some errors. My objective is to:
I'm OK removing all the rest. Those changes, AFAIK, are the ones we would like to enforce, will our linting checks allow us to (see #706 and openfisca/openfisca-france#1060). |
My best suggestion is to make the changes when you touch these files for some other reason. This spreads the changes over time and keeps them correlated with functional changes. |
Spring is here
flake8-bugbear
recommendations