At the url is a tarbz2ball of kdepython, the python bindings located in kdebindings. Some mapping in kde-functions.eclass is also required. It installs for me just nicely, and here's the output from an import test script included with the upstream package: localhost pykde # python importTest.py Testing PyKDE module imports Modules built: dcop kdecore kdesu kdefx kdeui kio kutils kfile kparts khtml kspell kdeprint kmdi Importing: dcop kdecore kdesu kdefx kdeui kio kutils kfile kparts khtml kspell kdeprint kmdi It seems to import ok, but I haven't had a chance to test core interface yet. Right now I have it in kde-base/kdepython as kdebindings is part of kde-base.
Created attachment 61413 [details] kdepython-3.4.1.ebuild For consistancy, the ebuild.
Created attachment 61414 [details, diff] no-gtk-glib-check.diff borrowed from dcoppython
kdebindings/python is a copy of pykde+pyqt+sip, for which we already have three separate ebuilds outside kde-base (see kdebindings/python/README.copy). Although, I've always been unsure about the statement there saying these versions have been 'patched to work out of the box with this version of KDE.' What are those diffs and what is their significance? Would like to receive illumination about this. Other than that, is there a need for this ebuild? I'm quite happy with the other herds managing at least some of the kdebindings subpackages :-)
Have a look at kde-base/pykde.
