-
Notifications
You must be signed in to change notification settings - Fork 8
Part 2/3 of Cookiecutter pre-commit workflow (flake8) #54
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
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.
great work, please see inline comment.
# normalized_grid / stretching_factor, normalized_grid, self.iq, left=0, right=0 | ||
# ) | ||
|
||
# E731 do not assign a lambda expression, use a def |
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.
remove this comment. Less chatter is better in the future, though I appreciate you wanting to communicate with me what you are doing (I think I can figure it out though.
For these lambda flake8 errors we would normally see if the function is being used in more than one place, and if it is, define a private function somewhere outside the main part of the code. If it is only being used in one place, we would simply move the lambda to where it is being used (so not assign it to a variable and then put the variable where it is being used, or we could put a # noqa: E731
at the end of this line so we leave it as is but it won't fail flake8.
How do we decide? the objective of all of this is not to pass flake8 but to make the code better, so the choice we make is the one that will make the code the best.
Also, in general, don't leave commented code in there, just delete it. Again, I appreciate the impulse (more transparency) but we don't want to carry around every old version of code in hte future.
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. A new pull request addressing your feedback has been made: #56
this workflow is spot on. I think you know, but just to say, you only have to connect to upstream and fetch once-and-done. Once you fetch, you should be able to just |
Once-and-done, confirmed! @sbillinge |
As instructed in #53 (review), here, I created a branch called
flake8
from the upstreamcookie
branch.Changed:
Just to confirm my workflow: