More useful printing for Pyreverse #8973
Description
Current problem
When Pyreverse runs, it prints out a bunch of "parsing" messages:
$ pyreverse pylint/pyreverse/
parsing pylint/pyreverse/__init__.py...
parsing /home/nick/pylint/pylint/pyreverse/inspector.py...
parsing /home/nick/pylint/pylint/pyreverse/plantuml_printer.py...
parsing /home/nick/pylint/pylint/pyreverse/printer.py...
parsing /home/nick/pylint/pylint/pyreverse/mermaidjs_printer.py...
parsing /home/nick/pylint/pylint/pyreverse/writer.py...
parsing /home/nick/pylint/pylint/pyreverse/__init__.py...
parsing /home/nick/pylint/pylint/pyreverse/dot_printer.py...
parsing /home/nick/pylint/pylint/pyreverse/main.py...
parsing /home/nick/pylint/pylint/pyreverse/printer_factory.py...
parsing /home/nick/pylint/pylint/pyreverse/diadefslib.py...
parsing /home/nick/pylint/pylint/pyreverse/utils.py...
parsing /home/nick/pylint/pylint/pyreverse/diagrams.py...
This is verbose and also not very useful. It's not even useful for debugging Pyreverse itself, since the parsing happens early on and errors generally happen later.
Desired solution
It would be cool if Pyreverse printed something more useful. Maybe some statistics or something?
Additional context
No response