[maemo-developers] telepathy-python bindings
From: Iñigo Illán Aranburu kodeport at terra.esDate: Fri Apr 27 18:37:03 EEST 2007
- Previous message: LED API
- Next message: telepathy-python bindings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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? P.D: I get the traceback on both SDK_ARMEL and SDK_X86. P.D.D: AFAIK Ubuntu Edgy sells with this versions of both telepathy and dbus bindings. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.maemo.org/pipermail/maemo-developers/attachments/20070427/bb1768aa/attachment.htm
- Previous message: LED API
- Next message: telepathy-python bindings
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]