Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Errors should be printed to stdout #201
In #26 and #29 you changed errors to be printed to stderr. But actually for a linter that's quite inconvenient when you want to post-process the output. I checked flake8, pycodestyle, pyflakes and they all write their errors to stdout (and so does mypy).
Only errors that cause the program to exit immediately (e.g. command line syntax or can't open file) should go to stderr; the expected output (diagnostics about doc style) should go to stdout.
Well, I side-stepped it using `2>&1`. :-) And now that I've installed flake8-docstrings all my flake8 runs automatically invoke it, which I don't appreciate. (I suppose there's a config flag to disable it.) But it does write to stdout, and the errors are parseable by Emacs command mode, so I'm still reasonably happy with it. Still, I think as a matter of principle all linters should write to stdout, not to stderr, since that is their principal output.