I've been investigating it a little bit. It seems utils/tiling.so uses Py_InitModule4 to load. I stumbled on some comment about renaming Py_InitModule4 to Py_InitModule4_64 on 64-bit machines so that 2.4 modules don't get loaded in 2.5 interpreter (http://svn.python.org/projects/python/trunk/Include/modsupport.h).
2.5 is the default Python version on Ubuntu (since Feisty?), so the cleanest and easiest (I believe) fix is to change the interpreter in gDesklets scripts. So, in /usr/lib/gdesklets directory change the first line in following files:
from "#!/usr/bin/env python" to "#!/usr/bin/env python2.4".
I can confirm that I've been able to run gdesklets this way, but some desklets don't function as expected; e.g. rythmlet, cpu, hdd status desklets, ...
I've been investigating it a little bit. It seems utils/tiling.so uses Py_InitModule4 to load. I stumbled on some comment about renaming Py_InitModule4 to Py_InitModule4_64 on 64-bit machines so that 2.4 modules don't get loaded in 2.5 interpreter (http:// svn.python. org/projects/ python/ trunk/Include/ modsupport. h).
2.5 is the default Python version on Ubuntu (since Feisty?), so the cleanest and easiest (I believe) fix is to change the interpreter in gDesklets scripts. So, in /usr/lib/gdesklets directory change the first line in following files:
gdesklets,
gdesklets-daemon
and optionally:
gdesklets-logview, migration- tool,
gdesklets-shell,
gdesklets-
from "#!/usr/bin/env python" to "#!/usr/bin/env python2.4".
I can confirm that I've been able to run gdesklets this way, but some desklets don't function as expected; e.g. rythmlet, cpu, hdd status desklets, ...