Search pylint configuration in setup.cfg and pyproject.toml

[pylint-bot]

Originally reported by: Fabio C. Barrionuevo da Luz (BitBucket: luzfcb, GitHub: @luzfcb?)

---

It would be great if pylint also seek the settings in a special section in setup.cfg file.

the same reasons as described by @bittner in
https://bitbucket.org/logilab/pylint/issues/121/search-pylintrc-in-config-directory#comment-13136390

---

• Bitbucket: https://bitbucket.org/logilab/pylint/issue/617

[pylint-bot]

Original comment by Claudiu Popa (BitBucket: PCManticore, GitHub: @PCManticore):

---

Why? This would complicate the configuration parsing and requires a lot of work to accommodate the internal implementation for little benefit. It will be yet another way to look for the configuration options, which increases the maintenance burden. And it will not be obvious where pylint will look first, in the setup.cfg or in pylintrc.

[pylint-bot]

Original comment by Fabio C. Barrionuevo da Luz (BitBucket: luzfcb, GitHub: @luzfcb?):

---

if the "pylintrc" file exist, stop search and get settings .

if the "pylintrc" file does not exist, verify that "setup.cfg" file exists.

If "setup.cfg" exist, get the settings.

if "pylintrc" file and "setup.cfg" exist, ignore "setup.cfg"

to make obvious what order the pylint use, just enter in the documentation something like:

pylint seeks the configuration file in the following order:

1 - project_dir/pylintrc
2 - project_dir/setup.cfg 
3 - ~/.pylintrc
4 - foo another location

[pylint-bot]

Original comment by Peter Bittner (BitBucket: bittner, GitHub: @bittner?):

---

JFYI, I had prepared pull request #276 to implement those changes. It was rejected, though.

[matrixik]

https://github.com/python/mypy added support for setup.cfg in python/mypy#2761

[sobolevn]

setup.cfg should be the default place to configure things.

[NeilGirdhar]

@PCManticore It might be good to take a look at this again if you haven't recently.

[PCManticore]

If pylint should support an additional format, that should be pyproject.toml not setup.cfg. setup.cfg doesn't seem to support nested sections, as our INI structure does, unless I'm missing something.

[sobolevn]

@PCManticore it is possible via something like this:

[pytest]
general_options = ...

[pytest.messages]
messages = ...

But supporting pyproject.toml is a good thing too.

[PCManticore]

If that's the case then, I don't mind supporting setup.cfg and pyproject.toml.

[pradyunsg]

@PCManticore Could you update the issue title to reflect the current plan moving forward?