-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Feature/pep8 #607
Feature/pep8 #607
Conversation
You have style errors. See them below. ./tests/integrations/test_full_pipeline.py:53:55: W292 no newline at end of file |
Another option is to use https://github.com/psf/black, it makes life easier IMHO. |
I guess in the end it boils down to a matter of taste and I (personally) do not like the black decisions that much 🤷♂️ |
My suggestion: lets start with that (which is "easier" to digest) and see how people like it. |
Feel free to merge it when it is ready, I will take care of rebasing my branches. |
I used flake8 and pylint in the past. Pylint is super aggressive. Flake8 was nice. We could add it to the travis build? |
This PR adds a github action (which is the CI tool of github) to do a pycodestyle check (which is exactly pep8 with some additional 120 column size setting). |
@MaxBenChrist Any more thoughts or can I merge? |
f0b83ec
to
28461df
Compare
I know. This is the PR basically everyone hates.
But, for a modern python package we should also comply to pep8, so I added a github action to check exactly this + some settings (line length = 120).
I also pep8-ified everything, which means we have a large PR but no changes except whitespace and alike.
Tests will hopefully show that :-)