pylintc for new code: disable format checker

[MVrachev]

Description of the changes being introduced by the pull request:

By default pylint does format checks:
https://pylint.pycqa.org/en/latest/technical_reference/features.html?highlight=format#format-checker

The problem is we also use black and isort who have format checkers as
well. This makes pylint format checks obsolete.

Also, it's possible that you would want to disable a warning and you
can end up in the situation where you will have to disable it for
two tools altogether.

Signed-off-by: Martin Vrachev mvrachev@vmware.com

[MVrachev]

As Jussi has pointed out, even the pylint project had disabled format for pylint:
https://github.com/PyCQA/pylint/blob/main/pylintrc#L80 😆.

[coveralls]

Pull Request Test Coverage Report for Build 1425820471

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.01%) to 97.442%

---

Totals
Change from base Build 1390970499:	0.01%
Covered Lines:	3946
Relevant Lines:	4030

---

💛 - Coveralls

[MVrachev]

I am finding more and more checks for pylint that overlap with what black
I found one more check that overlaps with black work inconsistent-quotes
and another one that overlaps with what isort does wrong-import-order

@jku do you think we should disable those checks?

[jku]

If the checks are problematic, then sure why not. But let's not disable things if they're working fine

[jku]

I agree with this:

• black seems to do a good job of format enforcement
• if we need to add local disables (like we'd like to in some test code), having two checkers for the same thing is problematic

[MVrachev]

If the checks are problematic, then sure why not. But let's not disable things if they're working fine

Locally I noticed a couple of warnings from pylint when I wanted to prepare a pr for pylint.
I will wait to have #1658 merged and then propose a pr for pylint.
If those warnings are still visible then I will disable them there.

[jku]

Now that I think about it... you could remove the format checker configuration section from pylintrc as well: if it does not get used, it should not be there