Bug reports, feedback

You think you have found a bug in Pylint? Well, this may be the case since Pylint is under heavy development.

Please take the time to check if it is already in the issue tracker at

If you can not find it in the tracker, create a new issue there or discuss your problem on the mailing list.

The code-quality mailing list is also a nice place to provide feedback about Pylint, since it is shared with other tools that aim at improving the quality of python code.

Note that if you don’t find something you have expected in Pylint’s issue tracker, it may be because it is an issue with one of its dependencies, namely astroid.

Mailing lists

You can subscribe to this mailing list at

Archives are available at

Archives before April 2013 are available at


Pylint is developed using the git distributed version control system.

You can clone Pylint and its dependencies from

hg clone
hg clone
hg clone

Got a change for Pylint? Below are a few steps you should take to make sure your patch gets accepted.

  • Test your code

    • Pylint is very well tested, with a high good code coverage. It has two types of tests, usual unittests and functional tests.

      The usual unittests can be found under /test directory and they can be used for testing almost anything Pylint related. But for the ease of testing Pylint’s messages, we also have the concept of functional tests.

    • You should also run all the tests to ensure that your change isn’t breaking one. You can run the tests using the tox package, as in:

      python -m tox
      python -m tox -epy27 # for Python 2.7 suite only
      python -m tox -epylint # for running Pylint over Pylint's codebase
  • Add a short entry to the ChangeLog describing the change, except for internal implementation only changes

  • Write a comprehensive commit message

  • Relate your change to an issue in the tracker if such an issue exists (see this page of Bitbucket documentation for more information on this)

  • Document your change, if it is a non-trivial one.

  • Send a pull request from GitHub (more on this here)

Functional tests

These are residing under ‘/test/functional’ and they are formed of multiple components. First, each Python file is considered to be a test case and it should be accompanied by a .txt file, having the same name, with the messages that are supposed to be emitted by the given test file.

In the Python file, each line for which Pylint is supposed to emit a message has to be annotated with a comment in the form # [message_symbol], as in:

a, b, c = 1 # [unbalanced-tuple-unpacking]

If multiple messages are expected on the same line, then this syntax can be used:

a, b, c = 1.test # [unbalanced-tuple-unpacking, no-member]

The syntax of the .txt file has to be this:

symbol:line_number:function_or_class:Expected message

For example, this is a valid message line:

abstract-class-instantiated:79:main:Abstract class 'BadClass' with abstract methods instantiated

If the Python file is expected to not emit any errors, then the .txt file has to be empty. If you need special control over Pylint’s flag, you can also create a .rc file, which can have sections of Pylint’s configuration.