-
Notifications
You must be signed in to change notification settings - Fork 65
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
fix flake8 reported issues, run tests #36
fix flake8 reported issues, run tests #36
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.
Was black
run on this as well? If so, it might be best to have one commit to see what black
did, one for what isort
did, and then finally the by-hand changes.
That way, I can review the by-hand changes that were made separate from the automated changes.
No, didn't run black. Run flake8 and isort and manually fixed stuff reported there. |
Have you considered using |
pushed an additional commit with black run. |
Had to drop both isort and flake8 as they don't agree with black. |
Here is a PR which just applies |
If we take that PR in first, and then rebase this PR on that, we'll have just the fixes you have applied which will be a bit easier to review. |
ok, go ahead merging #37 and I'll rebase. |
Signed-off-by: Sandro Bonazzola <[email protected]>
moved to #38 due to master/main rename |
Cleaned up the code, added automated tests.
Not adding all the unit tests at once as they are failing on my laptop. I'll enable all tests in a different PR once this is in.
Coverage report: 25%
coverage.py v6.5.0, created at 2022-10-24 13:57 +0000
coverage.py v6.5.0, created at 2022-10-24 13:57 +0000
Signed-off-by: Sandro Bonazzola [email protected]