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
Enable pylint for the python tests #11600
Conversation
@gigiblender is there anyway to make it error for new tests? |
@Mousius I don't see a clean way to do this. We could have a temporary |
Hmmm, I'm unsure whether we want to fill the logs with pylint without actually halting the build? Methinks it's worth doing as you suggested and filtering out the files we know will fail - we then have to lint them ourselves as quickly as we can 😿 |
bf92d5e
to
72fe47a
Compare
…though there are formatting errors.
72fe47a
to
15c5122
Compare
@Mousius, I applied your suggestion. Please have a look when you get the time. |
Argh @gigiblender, I didn't realise we would only be able to specify |
@Mousius, I think the second option sounds better. We can add subdirectories to the list as we fix them and collapse the list in a single entry once all the tests pass the linter. I think I can close this PR. |
Sounds good to me @gigiblender, thanks for raising this and kickstarting the great linting of 2022! |
This PR enables pylint for the tests and addresses #11414.
There is a large number of tests that have formatting errors. See the file attached.
out.txt