strictness_medium needs to exclude C0325 from PyLint's output about prospector HOT 5 CLOSED

I've tried this on a (very small) test case and cannot reproduce it. Could you create a test case, or point me at the code you're running prospector against?

from prospector.

Sorry, ignore me, I was running under Python 3

from prospector.

I just did some testing. You'll have to filter on print as well as C0325 since that code is too generic and is also used for legitimate messes like Unnecessary parens after u'if' keyword

from prospector.

I've been agonising about this one for a little bit. I think that the problem is a pylint one rather than a prospector one. My own feeling is that print(blah) is a bit suspect in Python 2, and since pylint will not warn if from __future__ import print_statement is used, then the warning is valid.

Having said that, a separate warning for print statements vs other statements would be useful, as there are valid reasons to supress the former without supressing the latter.

Check out the discussion on the code-quality mailing list about this very issue : https://www.mail-archive.com/[email protected]/msg00202.html

I will create a pull request on pylint itself about this to create a new error message, which will make it a lot easier for prospector to ignore. It's not particularly easy to ignore messages based on context right now.

from prospector.

... just to log it correctly, for the record: it's from __future__ import print_function

from prospector.