Closed SimonSchick closed 1 year ago
This is probably an issue for 2.15.x
as well. Removed the Unreleased
label. Opened #8088 with a fix.
Are you sure we introduced this check in https://github.com/PyCQA/pylint/issues/7605 ?
Well it was modified a lot : https://github.com/PyCQA/pylint/pull/7628 based on https://github.com/PyCQA/pylint/pull/7514. I also consider making a special case for anti-commutative operator, I might as well :D
Are you sure we introduced this check in #7605 ?
I only checked git blame and saw that it was added last November, so I though it must have been released yet. Seems I was wrong 😄
Ho, because we release a lot of patch version it does not seem like it, but time fly and 2.15.0 was released in late AUGUST (!!)
Bug description
Currently this checker doesn't appear to pay attention to the context of a field lookup and assumes that as long as the field name matches it can proceed, example:
Configuration
Command used
Please don't scream, we need to move things around (suggestions welcome either way).
Pylint output
Expected behavior
The false positive should not be reported
Pylint version
OS / Environment
MacOS
Additional dependencies
No response