Jean-Michel Pichavant wrote:
Anyone having this issue with pylint 0.21 ?
Looks like the interface has changed.
In the pylintrc file, I used both
disable=E1103
and
disable-msg=E1103
without any success. (disable-msg was working in 0.20)
I notice the inline options have changed as well, using -e or -d to
enable disable msg. I seems the inline options are working.
Any clue ?
JM
Some more informations,
There may be a problem with the -E option to enable only the errors.
in pylint 0.20:
def disable_noerror_checkers(self):
[SNIP]
# if checker is already explicitly disabled (e.g. rpython),
don't
# enable it
if checker.enabled:
in pylint 0.21:
def disable_noerror_messages(self):
for msgcat, msgids in self._msgs_by_category.iteritems():
if msgcat == 'E':
for msgid in msgids:
self.enable(msgid)
else:
for msgid in msgids:
self.disable(msgid)
There is no more protection if the E[msgId] has been previously disabled
(with the rcfile for instance) and all errors will be enabled.
I don't know if it's intended, I hope it is not, cause the -E is very
usefull but, speaking for myself I still need to disable those erros
configured in the rcfile.
Example:
{jeanmic...@carpates ~/w2/tnt}rm foo.py ; echo 'foo # undefined' >
foo.py ; pylint -E -d E0602 foo [w2:TRUNK]
{jeanmic...@carpates ~/w2/tnt}rm foo.py ; echo 'foo # undefined' >
foo.py ; pylint -d E0602 -E foo [w2:TRUNK]
************* Module foo
E0602: 1: Undefined variable 'foo'
[1] 29060 exit 2 pylint -d E0602 -E foo
when -E is specified after -d E0602 it's reenabling this msgId.
JM
_______________________________________________
Python-Projects mailing list
[email protected]
http://lists.logilab.org/mailman/listinfo/python-projects
