Description
Originally reported by: Fergal Hainey (BitBucket: FerHai)
I'm using pytest and redefined-outer-name is a false negative in these cases as it's part of pytest's design. I'd like to run pylint over the whole project to flag things automatically before code reviews. I'd like to catch cases of redefined-outer-name outside the tests folder.
I could add comments to the modules but 1. that's a lot of comments and 2. changes will require changing as many comments.
What could be nice is looking up through basedirs of the file being linted for pylintrc files and taking config in closer pylintrcs as higher priority. Or maybe something in the project wide pylintrc to denote some config applies to a directory.
Would this be considered a good idea? I'm open to making a patch if it's considered worthwhile.