-
Notifications
You must be signed in to change notification settings - Fork 183
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
Lint drift detection part #262
Lint drift detection part #262
Conversation
Hi @garawalid. Thank you for keeping the linting efforts! I left a small comment that might address the cause why the tests are failing. |
@smastelini thanks for the review! I need also to fix some regression in the lint of |
Codecov Report
@@ Coverage Diff @@
## master #262 +/- ##
==========================================
+ Coverage 88.39% 88.42% +0.02%
==========================================
Files 185 185
Lines 13566 13571 +5
==========================================
+ Hits 11992 12000 +8
+ Misses 1574 1571 -3
|
Something wrong with flake8 and |
In fact, there is a bug in flake8 (pycodestyle) with W605 and W503. I reported it here PyCQA/pycodestyle#949. I'll disable both rules for instance! |
It was a mistake in the |
Thank you for the hard work @garawalid. I'll proceed to review the PR. |
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.
Thank you again @garawalid for the linting efforts. I finished a first pass through the changes and let some comments and questions. It's looking pretty good so far!
Thanks @smastelini for the review. I think your |
Thanks for the explanation and for pointing me out to these guidelines, @garawalid. In fact, I found these W503 violations visually :-) Although W503 is ignored by default, (and only for readability and aesthetic purposes) I personally would prefer to enforce this rule. But it is worth discussing further. Any thoughts on that matter, @jacobmontiel? |
@smastelini
I ve been reading some comments about W503 & W504. And it sounds that the community didn't reach a final agreement yet. |
Hi @garawalid, you convinced me hahaha. I would say, let's go for W504 (even if we do not enforce it in our checks). What do you think @jacobmontiel? |
@smastelini sorry for the late response, I missed some comments. |
Hi @garawalid, thanks for the changes. I left some additional comments and resolved some of the pending items that were already solved. |
Thanks Walid for your linting efforts! This PR is now ready to be merged. |
Thanks @smastelini for your time and the review! |
Part of #219