Thanks Wil. We also use pylint with the violations plug-in, but I was hoping that I can maybe configure this check script separately. The pylint output is still a bit too much, and it would be useful to have this separately.

The things it will report on are about the same as pylint, but since Hudson just uses shell scripts you could have it run and if there is output email it to the committer. The output isn’t in the standard violations format so you can’t just plug it in to that. We use it more as a “run before commit” and “run when code reviewing” tool.

Hi Wil. Were you able to integrate Jeff Balogh’s check script with Hudson?

Not his script, but we’re using the Violations plug-in with the output of PyLint which gives us close to the same thing. The script to run it is here and here is an example report