Hide Forgot
Description of problem: TypeError: GObject.__init__() takes exactly 0 arguments (1 given) Already fixed in Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697204#32 Any chance of a patch? Version-Release number of selected component (if applicable): exiv2-0.23-4.fc19.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Triaging to libgexiv2 component
(In reply to James Patterson from comment #0) > Description of problem: > TypeError: GObject.__init__() takes exactly 0 arguments (1 given) > > Already fixed in Debian: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697204#32 > > Any chance of a patch? Actually, no. This is the same result but achieved by different means. Thank you for pointing me in the right direction. The problem is that the missing files for python support are in the separate package (libgexiv2-python2). Without this package you get error as shown above. However, when you install this package (and if no other application requires it is not installed by default), everything works as it should: matej@wycliff: Vídeň$ ipython Python 2.7.5 (default, Aug 20 2013, 06:42:55) Type "copyright", "credits" or "license" for more information. IPython 0.13.2 -- An enhanced Interactive Python. ? -> Introduction and overview of IPython's features. %quickref -> Quick reference. help -> Python's own help system. object? -> Details about 'object', use 'object??' for extra details. In [1]: from gi.repository import GExiv2 In [2]: im = GExiv2.Metadata('p20021208_120000(5).jpg') In [3]: dir(im) Out[3]: [ ... very very long list of available methods deleted ...] In [4]: type(im) Out[4]: gi.overrides.GExiv2.Metadata In [5]: I know that this is inconvenient, but unless we decide to have this python2 support installed per default (and I don't see the reason why we should), this is as they say a feature rather than a bug. I am sorry (I have been bitten by this myself).
Thanks.