Pylint output is too verbose

[cdyson37]

In particular. since at least 1.8.1, it now prints the location of the config file on every invocation. This results in a lot of spam if you use a parallel build/test system.

It would be good to have an option to emit not output unless there are warnings. Silence is golden :) In fact I think things like the location of the config should only be printed if the user requests additional verbosity.

[dstromberg]

I like silence unless a problem is found. That's one of the goals of http://stromberg.dnsalias.org/~strombrg/this-pylint/ It's just a pylint wrapper. HTH.

…

On Thu, Jan 25, 2018 at 4:04 AM, cdyson37 ***@***.***> wrote: In particular. since at least 1.8.1, it now prints the location of the config file on every invocation. This results in a lot of spam if you use a parallel build/test system. It would be good to have an option to emit not output unless there are warnings. Silence is golden :) In fact I think things like the location of the config should only be printed if the user requests additional verbosity. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1853>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA0yGjCmI09VvGalMGmxDO2SLClRLCnEks5tOG23gaJpZM4Rsv4z> .

-- Dan Stromberg

[PCManticore]

Sounds like a good idea, we can definitely silence this message unless a verbose option is given.

[Jitsusama]

@PCManticore; I was curious if any work was planned around this? When integrating pylint into my CD life-cycle, I'm getting a tonne of spurious logs while it validates code style.

[dstromberg]

On Mon, Apr 9, 2018 at 7:25 AM, Joel Gerber ***@***.***> wrote: @PCManticore <https://github.com/PCManticore>; I was curious if any work was planned around this? When integrating pylint into my CD life-cycle, I'm getting a tonne of spurious logs while it validates code style.

I like the stylistic warnings, but perhaps try --errors-only ?

…

-- Dan Stromberg

[PCManticore]

No work has been planned, feel free to submit a PR if you have some time!

[Jitsusama]

@PCManticore; I haven't dug into pylint's code-base yet. Do you have any recommended area of this code-base to start looking at if I were to introduce this feature/change myself?

[PCManticore]

@Jitsusama You might look into config.py, where this log actually happens. The flag can be added to lint.py, more exactly in the Run class, after which it can be propagated into the config. We already have a parameter for quiet here (https://github.com/PyCQA/pylint/blob/975e08148c0faa79958b459303c47be1a2e1500a/pylint/config.py#L463), but needs to be passed down as an option from the CLI. Let me know if you need any help!

[Jitsusama]

Thanks @PCManticore, I'll take a look at that!

[Jitsusama]

@PCManticore; just to verify, is your preference still to silence by default and only present when pylint is in verbose mode as per #1853 (comment)?

[Jitsusama]

@PCManticore; just bumping this thread as I didn't get a reply to my last question.

[PCManticore]

@Jitsusama yes.

[PCManticore]

A verbose mode was added recently in the master branch. You can now enable various verbose messages with pylint -v.