Skip to content
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.

Sign up for GitHub

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

Jump to bottom

pylint style output #33

Closed
techdragon opened this issue Jul 23, 2014 · 0 comments
Closed

pylint style output #33

techdragon opened this issue Jul 23, 2014 · 0 comments

Comments

@techdragon
Copy link

for ci-tools designed to parse pylint output
carlio added a commit that referenced this issue Sep 13, 2014
@carlio
[refs #33] Adding an output format for pylint -parseable style, which…
44a51a0 
… is used by several plugins and tools built on top of pylint. This will hopefully allow them to use prospector in place of pylint, although it may require a little bit of adaptation as prospector includes the source of the message as well as the message ID in the output
@carlio carlio closed this as completed Sep 24, 2014
carlio added a commit that referenced this issue Oct 20, 2014
@carlio
[refs #33 #50] Changing the pylint output formatter slightly so that …
afc3f9b 
…the output format is still handled correctly by the Jenkins violations plugin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@carlio @techdragon