Description

Added a new output format called pylint-parseable that follows this format: {path}:{line}: [{msg_id}({symbol}), {obj}] {msg}.
Updated a comment in the existing pylint formatter to reflect the actual formatting generated by the formatter and updated the docs accordingly.

Related Issue

Motivation and Context

When trying to integrate prospector into a CI/CD tool I realized that the pylint output does not follow the same output format as when using pylint --output-format=parseable (see Pylint 3.3.3 Documentation The existing format includes the character in the output which makes it difficult for it to be used as a drop-in-replacement. I added a new formatter that uses the format mentioned in the docs. I added a new formatter to avoid make a breaking change.

How Has This Been Tested?

Since this does not affect other areas it was only tested using some existing python projects to test the output.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• My change requires a change to the dependencies
• I have updated the dependencies accordingly
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.