Log from IRC [08:41:52] <thorbenk> Hello everyone :-) [08:42:37] <thorbenk> I have found a bug in the PyQt4 package: /usr/lib64/qt4/plugins/designer/libpythonplugin.so is linked against _python3.2_, whereas I have chosen python 2.7 as my main python via eselect [08:42:58] <thorbenk> I can see via ldd: libpython3.2.so.1.0 => /usr/lib64/libpython3.2.so.1.0 (0x00007f754e52e000) [08:43:34] <thorbenk> the problem: the libpythonplugin.so is used to load our designer-wrapped widgets written in python 2.7 [08:43:49] <thorbenk> Of course this fails, as it interpretes our code within python 3.2
Right, although not easy to fix. Maybe we should build libpythonplugin.so only for the active python version... other ideas?
I am not too familiar with these packages but KDE uses a wrapper[1] for pykde, perhaps we could borrow something like that? [1]: http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=blob;f=kde-base/pykde4/files/kpythonpluginfactorywrapper.c;
Ok so, I don't think versioning the plugin is feasible, however we might be able to let the user decide which python version the plugin must be built against via PYTHON_SINGLE_TARGET. @python: can we use python-single-r1 (in addition to python-r1) to achieve this?
(In reply to Davide Pesavento from comment #3) > Ok so, I don't think versioning the plugin is feasible, however we might be > able to let the user decide which python version the plugin must be built > against via PYTHON_SINGLE_TARGET. > > @python: can we use python-single-r1 (in addition to python-r1) to achieve > this? No, mixing the two is not possible. You can use 'python_wrapper_setup' in python-r1 to get the 'best' impl (that would be first enabled of 2.7, 2.6, 3.3, 3.2, ...) but nothing to get extra control.
PyQt4 is gone.
