Skip to content

Enabled pylint test for undefined-loop-variable

There are a lot of pylint warnings which don't really need to be strictly adhered to (and far too many to go through all at once), but I'd like to start enabling checks for the ones which are useful.

I'm not enabling/disabling tests in pyproject.toml since it's useful for the other tests to show up as warnings when editing files.

Starting with the undefined-loop-variable test, which is related to !538 (merged) (though apparently pylint doesn't recognize such issues in nested functions).

Merge request reports