-
Notifications
You must be signed in to change notification settings - Fork 3
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
Autofmt #71
Autofmt #71
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.
Yo, @bolliger32! I'm happy to give this a review this week. Could you give me a quick summary of what's going on and the goals here, I want to be sure I'm on the same page.
So we're hitting all the files with black and flake8 and we're getting the cleaned up files here. What rules/configs were used for the black and flake8?
What is the thinking about making black and flake8 checks part of an early test stage in CI/CD? i.e.: CI/CD rejects code changes unless it follows style?
Edit:
Also, I noticed our CI/CD check are already failing this. Is this something we should open a new issue for or is there a larger change this is a part of?
Hey @brews ! Yeah the summary is just that I started off just trying to clean things up just calling black on everything. We've added Previously master was failing so I thought that was the failures that this PR was running into, but I just rebased onto @delgadom 's changes (which are now passing on master) and it's still failing. Not sure what's going on as it's a sphinx-build issue that passes fine on my notebook... |
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.
In general reviewing "black everything" PRs is close to impossible so I'd strongly prefer separating this from everything else. Ok if we close this, run black as a separate PR, then try to tackle these remaining items one at a time?
Soundsd good to me! I'll keep this branch and then when we're ready to try again after theres a separate black-only PR we can merge again. |
closing - see #75 |
flake8 rhg_compute_tools tests docs
(some things in tests still raise flake8 warnings, but they are ones that are needed for pytest)Started off by just calling black and flake8 on everything. Flake8 caused me to spot a few typos that hadn't caught up to us yet but would soon.
isintance
instead ofisinstance
inkubernetes.py
warnings
inkubernetes.py