[Python-projects] __init__ method from a non direct base class <logilab.astng.Yes object at 0xb7f8392c> is called

Barry Scott barry.scott at onelan.co.uk
Tue Nov 21 12:35:14 CET 2006


Sylvain Thénault wrote:
> On Monday 20 November à 16:51, Barry Scott wrote:
>   
>> Alexandre Fayolle wrote:
>>     
>>> On Mon, Nov 20, 2006 at 02:25:19PM +0000, Barry Scott wrote:
>>>   
>>>       
>>>> Using pylint 0.12.1 I see a lot of these messages:
>>>>
>>>> W0233:1731:ActionItemEdit.__init__: __init__ method from a non direct 
>>>> base class <logilab.astng.Yes object at 0xb7f8392c> is called
>>>>
>>>> pylint is clear very broken. I found a email to this list in august from 
>>>> Skip Montano reporting
>>>> the problem. Give that pylint is unusable with this bug in place I'm 
>>>> surprised that the lastest
>>>> released kit contains this show stopper bug.
>>>>     
>>>>         
>>> If you read the recent archives you will see that this has been
>>> discussed, and it looks like it is a pygtk issue. 
>>>
>>> http://lists.logilab.org/pipermail/python-projects/2006-November/001002.html
>>>
>>> But since you provide no context, it is hard to tell if this is the
>>> case. 
>>>   
>>>       
>> My code does not use gtk. It is pure python (except for the extensions 
>> that ship
>> with python 2.4 itself).
>>     
>>> Thank *you* for helping us to see how important the issue is to you.
>>> Next time, try to be more helpful by providing a context to your bug
>>> report. And typing "please" and "thanks" probably won't tear your
>>> fingers apart will it? 
>>>
>>>   
>>>       
>> Please accept my apologies, I should know better.
>>
>> The code I'm running pylint against is very big it may take me a while 
>> to get a small
>> example that duplicate the error.
>>
>> Are there other situations that generate this false positive message?
>>     
>
> this is usually issued when pylint (well, astng...) isn't able to infer
> a parent class (import problem or whatever...).
>
>   
O.k. Thats good to know. Why not print a message that says this and 
hopefully include
information that can be used to track down the problem?

Barry



More information about the Python-Projects mailing list