On Tue, 18 Sep 2001, Tom Cato Amundsen wrote:
> Sorry, but your patch does not fix it for me. Have you
> tested the patch, or is it only theoretically proved to be
> correct? ;-)
>
> I removed all my old gtk/pygtk/multiple-pythonX.Y just to be safe,
> but using python 2.0 I still get a crash. Notice that the program
> crashes when we try to use self.b that as not yet been initialized.
> If we add
> self.b = 4
> to VClass.__init__, everything is ok.
>
> (Let me know when I start being annoying...)
I had tested your example with what was current in CVS at the time, and it
was crashing there. After applying the patch, it caused an exception as
it was supposed to. The exact results I got were (after applying the
patch, which is now in CVS):
>>> w = MWin()
Prepare to segfault
Traceback (most recent call last):
File "<stdin>", line 1, in ?
File "<stdin>", line 6, in __init__
AttributeError: b
>>>
This was one of the dirtier bits of code in pygtk that would be cleaner
using 2.2.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
