[pkg-kolab] kdepim and kolab

Sandro Knauß mail at sandroknauss.de
Mon Jun 23 10:54:38 UTC 2014


> One strange thing I encountered with the updated libkolab source packaging
> is the lack of an __init__.py file in the kolab Python package provided by
> the python-kolab Debian package. This means that it isn't possible to
> import from kolab in a Python program, affecting pykolab. Do you see that
> problem as well?
> The python-kolab.install file within libkolab looks like this:
> usr/lib*/python*/*-packages/kolab/_shared.so
> usr/lib*/python*/*-packages/kolab/shared.py
> usr/lib*/python*/*-packages/kolab/_calendaring.so
> usr/lib*/python*/*-packages/kolab/calendaring.py
> usr/lib*/python*/*-packages/kolab/_icalendar.so
> usr/lib*/python*/*-packages/kolab/icalendar.py
> usr/lib*/python*/*-packages/kolab/_kolabobject.so
> usr/lib*/python*/*-packages/kolab/kolabobject.py
> Adding an entry for the __init__.py file fails because there isn't one
> already present or subsequently generated. What am I missing here?

Well yes i see the same issue here - actually upstream doesn't create this 
file. But you can easily create one (it is just an empty file, so touch should 
be your friend :) And you can use pykolab by using the direct import 
kolab.foo. The debian package should  ship an __init__.py.



More information about the pkg-kolab-devel mailing list