Automatically respect .pylintrc files in subdirectories

Environment data

VS Code version: 1.19.0 Python Extension version: 0.9.0 (14 December 2017) Python Version: 3.6.1 OS and version: Windows 10 Home, Version 1703, OS-version 15063.483

Actual behavior

.pylintrc files in a directory in the workspace are not automatically found by pylint

Expected behavior

• .pylintrc files found in a directory should be automatically respected for that folder and all sub-directories.
• New .pylintrc files in sub-directories should take precedence over parent directories .pylintrc files

This is how it works when running the pylint command via terminal. .pylintrc files are automatically respected without supplying them specifically via the option --rcfile

Note that I am unsure if other options are respected as defined here https://pylint.readthedocs.io/en/latest/user_guide/run.html#command-line-options

Steps to reproduce:

• Create a .pylintrc file in a directory in the workspace and notice how the rules defined are not respected

[JamesMessinger]

I am also having this issue. However, I’ve been able to workaround it by using the python.linting.pylintArgs setting to explicitly point to the .pylintrc file

  "python.linting.pylintArgs": [
    "--rcfile",
    "${workspaceFolder}\\.pylintrc"
  ],

Btw… this issue seems related to https://github.com/DonJayamanne/pythonVSCode/issues/117

[mgasner]

This is surprising behavior! Especially in larger repositories or monorepos, it’s likely that different pylint standards will be applied to different parts of the directory tree or even to submodules. For example, you might want to enforce the existence of module-level docstrings in a library, but not in test files.