-
Notifications
You must be signed in to change notification settings - Fork 21
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 warnings #97
Conversation
…k before binary operator
…fix_flake8_warnings
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.
Thanks for all this hard work!
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.
Thanks!
@@ -0,0 +1,36 @@ | |||
#!/usr/local/lcls/package/python/current/bin/python |
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.
Do we still need this file?
🥳 🍾 🎆 |
* ignore too many hashes for block-comment, and contraversial line break before binary operator * flake8 fixes * remove lambda for flake8 * changing unittest command, change from python-app to python-package workflow. * add requirements for workflow install step * make callback a callable for test to pass * add exception for line-length * remove unnecessary file --------- Co-authored-by: matt <matt@SLACMachine.myguest.virtualbox.org>
Summary of Changes
Most of the changes include reformatting or removing unused variable/imports.
I have added a
.flake8
file that allows the errors/warnings to be configured. For example, there is an allowable line-length that is configured in that file to be 120 (PyCharm default), as well as ignoring some other warnings.To Check
96_fix_flake8_warnings
) in your local repositorypython3 -m pip install flake8
) if you do not already have itflake8 .
in the lcls-tools repositoryOther notes
The first stage of the pipeline should pass after these changes have been merged and we can move onto fixing the unit-tests.
closes #96