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
ansible-test - Update sanity test requirements #78324
Conversation
Update pylint to 2.9.6 to get around a false positive for undefined-variable in a decorator. pylint-dev/pylint#3791
I figured this would break some things, but I was hoping it was a small enough change it wouldn't. |
Ah, that's another bug in |
Turning into a bit of a rabbit hole... |
This is the minimum version that addressesd the original error I was seeing that does not fail with other pylint bugs.
I disabled a few checkers that are new for pylint 2.10. I'm not sure if those should be disabled in the |
Only the use-dict-literal is failing, but it’s probably best to disable the other rules as well so collection authors don’t get any unpleasant surprises.
The test
|
@samdoran I have a local branch where I've started work on upgrading |
@mattclay Sounds good! I'll close this. |
SUMMARY
Update pylint to 2.9.6 to get around a false positive for
undefined-variable
in a decorator.pylint-dev/pylint#3791
ISSUE TYPE
COMPONENT NAME
test/lib/ansible_test/_data/requirements/sanity.pylint.in
test/lib/ansible_test/_data/requirements/sanity.pylint.txt
ADDITIONAL INFORMATION
Simple reproducer
Command output
I've found I can work around this by using different variable names in the comprehension than the function signature.