[maemo-developers] telepathy-python bindings

[From: Lauro]

On 4/27/07, Iñigo Illán Aranburu <kodeport at terra.es> wrote:
>
>  Hi!
>
>  I have been trying to package the python bindings for telepathy (version
> 0.13.3 of the bindings) using bora's 3.1 sdk. I'm getting this traceback:
>
>  File "setup.py", line 4, in <module>
>     from telepathy import __version__
>  File "/home/ignacius/msn/telepathy-python-0.13.3/telepathy/__init__.py",
> line 28, in <module>
>      import telepathy.server as server
>  File
> "/home/ignacius/msn/telepathy-python-0.13.3/telepathy/server/__init__.py",
> line 23, in <module>
>      from telepathy.server.connmgr import *
>  File
> "/home/ignacius/msn/telepathy-python-0.13.3/telepathy/server/connmgr.py",
> line 26, in <module>
>      class ConnectionManager(dbus.service.Object):
>  File
> "/home/ignacius/msn/telepathy-python-0.13.3/telepathy/server/connmgr.py",
> line 104, in ConnectionManager
>      @dbus.service.method(CONN_MGR_INTERFACE, in_signature='s',
> out_signature='a(susv)')
>  File
> "debian/python2.5-dbus/usr/lib/python2.5/site-packages/dbus/decorators.py",
> line 24, in decorator
>  File "dbus_bindings.pyx", line 84, in
> dbus_bindings.SignatureIter.next
>  TypeError: exceptions must be strings, classes, or instances, not type
>
>  I think the problem is somewhere inside dbus bindings. Has anyone the
> expertise for helping me?
>

Iñigo, this happens due to some problems with C code generated by
Pyrex (wich is used in the dbus bindings). This is already fixed on
trunk and will be shipped on the next release.

Bug reports below:

Bug #560 - https://garage.maemo.org/tracker/index.php?func=detail&aid=560&group_id=40&atid=229
Bug #561 - https://garage.maemo.org/tracker/index.php?func=detail&aid=561&group_id=40&atid=229


Regards,
-- 
Lauro ("lmoura" on Freenode)
CIn/UFPE
http://lauro.wordpress.com