-
Notifications
You must be signed in to change notification settings - Fork 25
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
Start using isort
and black
code formatters
#80
Start using isort
and black
code formatters
#80
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #80 +/- ##
==========================================
- Coverage 54.17% 54.03% -0.14%
==========================================
Files 25 25
Lines 3055 3046 -9
==========================================
- Hits 1655 1646 -9
Misses 1400 1400
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
de977c4
to
565b035
Compare
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.
Looks good, nice commit separation
Apply the the code formatters:
isort
to consistently sort importsblack
to consistently format the code base.These will help keep the codebase consistently formatted, and are recommend to be used in conjunction with the
ruff
linter thatstpipe
is already using.I also adjusted the the line-length restriction from 130 down to a more reasonable (and the
black
standard) length of 88.Note that this is base on PR #79 and so it should be merged after it.