Searching for an answer on Pylint's mailing list brings no interesting results.
Pylint is known to be very customizable, so I guess this should be possible...
The reason I would like Pylint to check compliance with PEP8 is because
- PyDev has much better support for Pylint than it has for PEP8.
- It's easier to have one tool doing all checks than having to use two.
I also asked this question on Pylint's mailing list at http://thread.gmane.org/gmane.comp.python.logilab/1039
Example of diagnostic messages from PEP8 which I don't get from Pylint:
- E203 whitespace before ':'
- E225 missing whitespace around operator
- E251 no spaces around keyword / parameter equals
- E301 expected 1 blank line, found 0
- E303 too many blank lines
- E501 line too long (90 characters)
- W291 trailing whitespace
- W292 no newline at end of file
- W293 blank line contains whitespace