Re: [code-quality] False negative for pylint E0203 when using += operator?

On 17 mars 19:40, Andreas Maier wrote: > Hi, Hi, > I am using PyLint 1.1.0 with Python 2.6, and found that the following > code does not raise E0203 "Access to member '%s' before its > definition line %s", as it should: > > class MyClass1(object): > def __init__(self): >

[code-quality] False negative for pylint E0203 when using += operator?

Hello Sylvain, Thanks for your quick response. I have created Issue #164: https://bitbucket.org/logilab/pylint/issue/164/ Andy Am 18.03.2014 09:32, schrieb Sylvain Thénault: IIRC it has indeed already been mentioned but I'm not sure there is a proper issue for it. And your report is nice, so

Re: [code-quality] False negative for pylint E0203 when using += operator?

On 18 mars 10:18, Andreas Maier wrote: > Hello Sylvain, > Thanks for your quick response. > > I have created Issue #164: > https://bitbucket.org/logilab/pylint/issue/164/ thanks ! I'm afraid the fix won't be so quick though ;) -- Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.6

[code-quality] False positive for E1101 on function member 'func_name'

Hi again, I am using pylint 1.1.0 for Python 2.6 code. The following code: def myfunc(): print myfunc.func_name# Incorrectly raises E1101 print myfunc.__name__ # Correctly passes causes this pylint error to be raised: E1101: Function 'myfunc' has no 'func_name' memb

Re: [code-quality] False positive for E1101 on function member 'func_name'

On 18 mars 10:31, Andreas Maier wrote: > Hi again, Hi, > I am using pylint 1.1.0 for Python 2.6 code. > > The following code: > > def myfunc(): > print myfunc.func_name# Incorrectly raises E1101 > print myfunc.__name__ # Correctly passes > > causes this pylint error

[code-quality] Making git and pylint interact

Hi! This is a question about making your favorite VCS and pylint interact. The idea is that sometimes there's a project and you're running pylint on it, but you want to distinguish among two kinds of errors: 1) Errors introduced by the last few commits. 2) Errors that have been around forever an

Re: [code-quality] Making git and pylint interact

On 3/18/14 6:27 PM, Anne Mulhern wrote: Hi! This is a question about making your favorite VCS and pylint interact. The idea is that sometimes there's a project and you're running pylint on it, but you want to distinguish among two kinds of errors: 1) Errors introduced by the last few commits.