1. Start up the python interpreter: $ python 2. Import the vte module: >>> import vte This results in the following error: Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initvte) Reproducible: Always Steps to Reproduce: 1. Start up the python interpreter: $ python 2. Import the vte module: >>> import vte Actual Results: Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initvte) Expected Results: No error. This bug appears to be caused by a change in version 1.2 of vte/python/vtemodule.c. For some reason, two suspicious underscores appeared in both the function name('initvte' to 'init_vte') and the first arg to Py_InitModule('vte' to '_vte'). I'm not a big python guy but I think the discrepancy between the function name and the name given to DL_EXPORT is to blame. I've already submitted this bug to the gnome bugzilla database: http://bugzilla.gnome.org/show_bug.cgi?id=150760 However, I figure its something we can easily fix with a patch so I'm submitting it here as well.
It looks like this has been fixed in the newer x11-libs/vte ebuilds. I am using x11-libs/vte-0.11.10-r1 with python2.3.4 and do not see the error.
>>> import vte Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dynamic module does not define init function (initvte) on my a64 machine (gentoo 2004.3)
Created attachment 49649 [details, diff] ..../vtemodule.c.diff Please apply to vte-0.11.11/python/vtemodule.c (The Debian guys had the same problem, same fix)
In portage now. Thanks for the report and the patch.
*** Bug 81006 has been marked as a duplicate of this bug. ***
