.. -*- coding: utf-8 -*-

Version 0.19.0
--------------
:publication date: 2009/12/18
:expected date: n/a

Ticket #18308 fulltest.sh refers to deleted runtests.py
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: resolved

runtests.py was removed in changeset 476:622d0bbc57c0, yet fulltest.sh still
remains and refers to it.

I'm guessing that the new "preferred" way to run unit tests is with pytest? At
the very least this file was useful for explaining the best way to run tests, so
it should be fixed rather than removed! :-)

Ticket #9334 C0103 false positive on __class__
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.000
:state: rejected

When run on this code:

.. sourcecode:: python

class Clazz(object):

def changeType(self, newClass): self.__class__ = newClass

pylint issues this message::

C0103: 4:Clazz.changeType: Invalid name "__class__" (should match
_?_?[a-z][a-zA-Z0-9]{1,30}$)

It is true that the name "__class__" does not match the configured naming
convention. However, since it is a builtin Python name, changing the name is not
possible.

Ticket #18949 checker for string formatting
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.300
:state: resolved

See http://lists.logilab.org/pipermail/python-projects/2009-November/002086.html
and http://lists.logilab.org/pipermail/python-projects/2009-November/002111.html

Ticket #18862 E0601 false positive with lambda functions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.200
:state: resolved

James Lingard reported...

The following program:

.. sourcecode:: python

def f(): g = lambda: x x = 1 print g()

generates the following unnecessary error::

E0601: 2:f.<lambda>: Using variable 'x' before assignment

Note that the following program doesn't generate the error:

.. sourcecode:: python

def f(): def g(): return x x = 1 print g()

I think it would make sense for this warning to treat lambda expressions the
same as function definitions.

Ticket #18948 fix spelling mistakes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

http://lists.logilab.org/pipermail/python-projects/2009-November/002093.html

Ticket #5821 implement a quiet mode to run as a library
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.100
:state: resolved

implement a quiet mode so that it can be run by some other program and return an
exit code without polluting the standard output.

Comments ::

  On 2009/11/24 10:23 - sthenault wrote :
  you can already do this by using a custom reporter.

Ticket #10056 Many test files missing from pylint tarball
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

The Pylint 0.18.0 tarball is missing a number of files in test/ (all files that
don't start with test_ except fulltest.sh) that are still in Mercurial. This
means the tests can't be run from the downloaded tarball.

Ticket #17958 pylint -e must not silence Fatal messages
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: bug
:load: 0.100
:state: resolved

Typical usage for "-e" being to catch most critical problems, having it hiding
fatal messages is quite counter-productive. It should indeed mean "only the
messages of severity ERROR and above are displayed".

Ticket #4004 update pylint.el
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:type: enhancement
:load: 0.500
:state: resolved

Rewrite or update pylint.el so as to:

- not use Fn keybindings - not use the my-so and so function names - run with
emacs22 - use a pylint-option variable to handle additional options

See debian bug report for more information.

Comments ::

  On 2007/07/13 11:22 - sthenault wrote :
  the two first point are done. Dunno about the third. The fourth isn't.
  > On 2009/09/02 06:27 - anon wrote :
  > 3) was raise probably because pylint was using only written for
  > python-mode.el. r480 corrected this by detecting the correct mode keymap. 4)
  > was fixed in #3857.