On Wed, Apr 14, 2004 at 01:02:40PM +0200, Antoon Pardon wrote:
> On Tue, Apr 13, 2004 at 10:59:22AM +0200, Johan Dahlin wrote:
> > tis 2004-04-13 klockan 07.51 skrev Benjamin Collar:
> > > Greetings
> > >
> > > I've written some *incorrect* code that causes python to segfault. Would this
> > > be a python bug or a pygtk bug?
> >
> > Actually this is your bug. It's discussed in
> > http://bugzilla.gnome.org/show_bug.cgi?id=96658 which was closed as
> > WONTFIX.
> >
> > The solution is to remove the empty constructor or add
> > self.__gobject_init__()
>
> That it is his bug, doesn't contradict that it is someone
> else's bug too. If a bug in the python code triggers a
> segmentation violation, then I consider that a bug either
> in the python interpreter or the module used.
Well, I tend to agree. The problem is that technically there doesn't
seem to be a very good way to detect and avoid this sort of problem; at
least that was the situation Johan James and I discussed over a year
ago. If you'd like to chip in and try and cook up a better solution, the
issue is currently WONTFIXed at bug 96558:
http://bugzilla.gnome.org/show_bug.cgi?id=96658
I'm sure the WONTFIX would be reconsidered if someone cooked up a decent
patch to fix the issue. I'm just not sure it's that easy to do <wink>
Take care,
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
