Conversation
afe2229 to
03f2d3c
Compare
Codecov Report
@@ Coverage Diff @@
## master #8409 +/- ##
==========================================
- Coverage 67.65% 67.61% -0.05%
==========================================
Files 448 448
Lines 22506 22482 -24
Branches 2364 2364
==========================================
- Hits 15227 15201 -26
- Misses 7141 7143 +2
Partials 138 138
Continue to review full report at Codecov.
|
villebro
left a comment
There was a problem hiding this comment.
Nice work! LGTM, looks very clean. Just a few comments, mostly out of scope-stuff. @mistercrunch I propose including this in the 0.35 release, as these changes will most likely cause widespread conflicts when picking cherries for upcoming patch releases on the 0.35 branch.
villebro
left a comment
There was a problem hiding this comment.
LGTM. I will open a separate PR to address the out of scope comments.
|
Confirmed with I can merge this, we're laying more refactors on top of this. |
* [ci] Deprecate flake8 * Addressing @villebro's comments
CATEGORY
Choose one
SUMMARY
This PR deprecates
flake8(where we were usingflake8-import-orderandflake8-mypy) in favor of usingisortandmypydirectly. Notepylint(which we use though in many cases have warnings disabled) can be viewed as a supersetflake8.The reasons for the changes are:
flake8-mypyhas missed some issues thatmypydiscovers (fixed in this PR) and ignores some of themypysettings.flake8mostly for checking import order and typing now that we're usingblack. Note thatisortboth checks and formats.Also we were using
flake8for some other checks but simply ignoring these via# noqawhich lacked specificity, i.e., reading the code it's not apparent what we're ignoring. Ideally we should be upping ourpylintgame as these checks would be caught bypylint. Currently many files havepylintwarnings ignored and we have disabled a number of checks in the.pylintrcfile per here. In the future we enforcepylintfor all errors and warning and enable most (if not all) checks.There are a few cases where I used
# type: ignoreas I ended up going down a rabbit hole when trying to resolve types. I think in the future we should try to re-enable these checks.TEST PLAN
CI.
ADDITIONAL INFORMATION
REVIEWERS
to: @betodealmeida @etr2460 @michellethomas @mistercrunch @villebro