Jacob Walls

I think "Using" is fine, since it's user-facing (from the user's perspective, pylint is about to "use" this file). > it's possible to print such message each time new config...

Hey @0nf thanks for updates! Really appreciate the follow-through here. So I guess my comment earlier this week was less about the message printed to the console, and more about...

My files look like this: ```py ~/ pylint/ pylintrc astroid/ pylintrc ``` If I cd to `~/astroid` and `pylint astroid`, I get astroid's pylintrc applied. If I cd to `~/pylint`...

Let me look a little closer to ensure the differences in output I'm seeing are resulting from the configuration file in use.

Yeah, I confirmed by changing pylint's pylintrc to just `disable=all` and then when I `cd /pylint && pylint astroid --use-local-configs=y`, the use-local-configs flag makes no difference -- either way I...

> Well, would it be correct to say that you are checking a module from sys.path in this case? Sorry, I should have clarified that in my example both pylint...

Thanks for the report. I'm hearing two requests. One is to distinguish: ```py def function2(): df = SomeType() return {k: k.lower() for k in df.columns} ``` from this, which is...

But my example shows that I tried that, no? I ran `pylint a.py b.py` and got a `no-member`.

Are you defining the class `SomeType` anew in each file? That could explain the difference.

Got it, I think I ran one of the `pylint a.py` runs with the wrong contents and got mixed up. Thanks for bearing with :pray: > I understand fixing this...