-
-
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
Avoid raising undefined-loop-variable
twice on same line
#6925
Avoid raising undefined-loop-variable
twice on same line
#6925
Conversation
Pull Request Test Coverage Report for Build 2483725205
π - Coveralls |
I spot-checked the messages from sentry, and found that they were duplicates that are now just emitted once. |
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.
While checking if self._loopvar_name(node)
is still being used I noticed that the other use is guarded by if self._is_undefined_loop_variable_enabled
.
This breaks useless-suppression
. We could fix that in this PR as well or do a follow-up.
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.
π
Nice catch @DanielNoord. Let's do a follow-up as it's another issue. |
Type of Changes
Description
See #6923 (comment) for report.
This call has been here since the initial commit, but nothing fails when I remove it. Let's see what the primer says.