[pygtk] pyGtk segfault comparing gtk.Image with 0

[John Finlay]

Pietro Battiston wrote:
> Il giorno sab, 17/10/2009 alle 20.49 +0300, Paul Pogonyshev ha scritto:
>   
>> Pietro Battiston wrote:
>>     
>>> Il giorno sab, 17/10/2009 alle 17.30 +0100, Tomeu Vizoso ha scritto:
>>>       
>>>> On Sat, Oct 17, 2009 at 17:12, René 'Necoro' Neumann <lists at necoro.eu> wrote:
>>>>         
>>>>> Well -- you are not initializing gtk.Image. So it's your very own
>>>>> mistake. I don't see a pygtk issue here.
>>>>>           
>>>> This is Python, any crash is a bug.
>>>>         
>>> Wait, wait.
>>>
>>> Read http://bugzilla.gnome.org/show_bug.cgi?id=561130 , then come back
>>> here and let's talk :-)
>>>
>>> Pietro
>>>
>>> (P.S: as you can desume from the page, I _would like_ to agree with you)
>>>       
>> You can still rightfully agree with him that it _is_ a bug.  Whether
>> it gets fixed is another point.
>>     
>
> What I mean is: where is it written that every crash is a bug, if Pygtk
> developers themselves are not so clear on that (and I'm possibly too
> ignorant)?
>
>   
this question has come around a couple of times before and I recall that 
each time it's deemed too impractical to catch every possible error to 
prevent a segfault.

John