After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 554443 - gobject.GObject's __init__() breaks the super(...).__init__() chain.
gobject.GObject's __init__() breaks the super(...).__init__() chain.
Status: RESOLVED DUPLICATE of bug 351566
Product: pygobject
Classification: Bindings
Component: gobject
2.14.x
Other All
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-30 14:29 UTC by Guillaume Emont (guijemont)
Modified: 2008-09-30 20:10 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement

Attachments
example code showing the issue (310 bytes, text/x-python)
2008-09-30 14:30 UTC, Guillaume Emont (guijemont) 		Details

Description Guillaume Emont (guijemont) 2008-09-30 14:29:09 UTC 
Classes inheriting from gobject.GObject cannot make sure all their __init__() methods are called. Inheriting from gobject.GObject makes you unable to call cousins' or brothers' __init__() implementations.

See example code:
 expected behaviour: Mum's __init__ is called, then Son's __init__
 current behaviour: Mum's __init__ is never called, only Son's is.
Comment 1 Guillaume Emont (guijemont) 2008-09-30 14:30:02 UTC 
Created attachment 119652 [details]
example code showing the issue
Comment 2 Paul Pogonyshev 2008-09-30 20:10:23 UTC 

*** This bug has been marked as a duplicate of 351566 ***