Make the verbose mode more talkative

[ulope]

Steps to reproduce

1. run pylint --verbose somepath

Current behavior

The config file used is printed

Expected behavior

pylint to be actually verbose. For example:

• print options set from the config file
• print files / modules as they are discovered
  • print ignore patterns that are / aren't matched
• print child checker jobs being started / stopped
• print files / modules as they are being checkd
• ...

pylint --version output

pylint 2.3.1 astroid 2.2.5 Python 3.7.4 (default, Sep 6 2019, 13:40:26) [Clang 10.0.1 (clang-1001.0.46.4)]

[PCManticore]

Thanks for opening an issue. While this would make sense, we haven't heard a lot of feedback that verbose needs to be more verbose than it is right now. It's also not a priority to make pylint more verbose, but if you're interested in taking this on, feel free to submit a PR to add some of these messages.

[Kristinita]

While this would make sense, we haven't heard a lot of feedback that verbose needs to be more verbose than it is right now.

Type: Question :question:

@PCManticore, 19 GitHub users have upvoted this issue. Is this enough to reopen the issue?

Thanks.

[Pierre-Sassoulas]

What most software I know do is to create level of verbosity to handle this. i.e. -v for minimal verbosity, -vv for more details, and -vvv for everything. This might make more sense here if we want to be able to really troubleshoot in verbose mode.