Seg, 2004-11-08 �s 15:56 -0200, Christian Robottom Reis escreveu:
> On Fri, Nov 05, 2004 at 03:33:44PM +0000, Gustavo J. A. M. Carneiro wrote:
> > > >   Yes.  I am a bad gnome-python maintainer and forgot to migrate some
> > > > gnome-python classes to the new property-based constructors, which allow
> > > > transparent __init__ parent chaining.  gnome.Canvas is still using old
> > > > constructor system, therefore you must replace this:
> > > >           gnome.canvas.Canvas.__init__(self, aa=aa)
> > > > with this:
> > > >           self.__gobject_init__(aa=aa)
> > > > (or something like that)
> > > 
> > > Ah, I see.  Is the old method forward-compatible (i.e., when the bug
> > > is fixed, will the old method still work?)?
> > 
> >   Yes.  __gobject_init__ may eventually become deprecated in pygtk 2.6,
> > not will be kept for compatibility.  We are forbidden to break API.
> > 
> >   And to answer kiko's earlier question: no, neither bug report nor cvs
> > commit to fix this yet :-P
> 
> How about you or someone who has a clue about this filing one so I can
> delete one more item of email from my inbox? :-)

  Don't bother.  Fixed in CVS.  I guess I was just waiting for the
weekend...

> 
> Take care,
> --
> Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3361 2331
-- 
Gustavo J. A. M. Carneiro
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
The universe is always one step beyond logic.

Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
pygtk mailing list   [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/

Reply via email to