pylint

I am evaluating pylint as source code checker and I would like to customize the maximum number of characters on a single line. I would like to use a configuration file. I've generated a template thanks to the --generate-rcfile command and I've made my modification. I am trying to run pylint --rcfile=myfile.rc but I can see that my changes are not taken into account by pylint. I've tried different location for my file : \Python26\Scripts\ and pylint.d in my user folder without any success. Does anybody know what I am doing wrong? Is it possible to use the configration file with pylint-gui? I

I saw I can change it per Eclipse instance using this solution. I would like to set it per project. Is it possible? sthenault This is not Eclipse specific, but it may help anyway. According to pylint command line options : You can specify a configuration file on the command line using the --rcfile option. Otherwise, Pylint searches for a configuration file in the following order and uses the first one it finds: pylintrc in the current working directory .pylintrc in the current working directory If the current working directory is in a Python module, Pylint searches up the hierarchy of Python

Starting with pylint-1.0.0 the --include-ids argument is no longer allowed. How do I get: ************* Module foo.bar E:199,11: Module 'yaml' has no 'scanner' member (no-member) ************* Module foo.baz W:153,27: Unused variable '_filenames' (unused-variable) to show the IDs (e.g. W0142), for each warning? The new way to specify this is the command line parameter '--msg-template={path}:{line}: [{msg_id}({symbol}), {obj}] {msg}' . 来源： https://stackoverflow.com/questions/18133264/how-do-i-get-pylint-message-ids-to-show-up-after-pylint-1-0-0

This question already has an answer here: PyLint message: logging-format-interpolation 1 answer I am using prospector to examine my code. Pylint returned a logging-not-lazy warning about my debug message. Line: 31 pylint: logging-not-lazy / Specify string format arguments as logging function parameters (col 16) Line: 42 pylint: logging-not-lazy / Specify string format arguments as logging function parameters (col 12) My code is: logging.debug("detect mimetypes faild because %s" % e ) How do I fix logging-not-lazy in pylint? Zada Zorg This mean, that you should rewrite your code as: logging

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

I have a module-level variable in my Python 2.6 program named "_log", which PyLint complains about: C0103: Invalid name "_log" (should match (([A-Z_][A-Z0-9_]*)|(__.*__))$) Having read this answer I understand why it's doing this: it thinks the variable is a constant and applies the constant regex. However, I beg to differ: I think it's a variable. How do I tell PyLint that, so it doesn't complain? How does PyLint determine whether it's a variable or a constant - does it just treat all module-level variables as constants? ChristopheD # pylint: disable-msg=C0103 Put it in the scope where you

We are using pylint within our build system. We have a python package within our code base that has throwaway code, and I'd like to disable all warnings for a module temporarily so I can stop bugging the other devs with these superfluous messages. Is there an easy way to pylint: disable all warnings for a module? enderskill From the PyLint FAQ With Pylint < 0.25, add # pylint: disable-all at the beginning of the module. Pylint 0.26.1 and up have renamed that directive to # pylint: skip-file (but the first version will be kept for backward compatibility). In order to ease finding which modules