New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enhancement 1070 file output #4339
Enhancement 1070 file output #4339
Conversation
…eNr33/pylint into enhancement-1070-file-output
I do not have the time to review everything right now, but isn't |
Do you mean that the command line/pylintrc parameter should be named simple "command" instead of "output file"? |
I was thinking the standard when available is |
I've seen both, but don't have a preference and don't know what is more common. Changed it to just |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great change on an old issue that needed fixing :)
Steps
doc/whatsnew/<current release.rst>
.Description
This PR is a proposal for closing #1070.
It adds a new option
--output-file
which can be optionally specified.If set, all messages and reports will be saved to the specified file instead of being printed to stdout.
It can be combined with all of the existing reporters/output formats.
Type of Changes
Related Issue
Closes #1070