GNOME Bugzilla – Bug 313454
Python module of vte can't be imported
Last modified: 2005-11-08 21:37:32 UTC
Please describe the problem: It isn't possible to import vte or vtemodule into python. Steps to reproduce: 1. $ python 2. >>> import vte Actual results: I get this error: Traceback (most recent call last):
+ Trace 62432
symbol: pyg_set_object_has_new_constructor Expected results: Does this happen every time? Other information: I have changed pyg_set_object_has_new_constructor(VTE_TYPE_TERMINAL); an line 1553 of python/vte.c to pygobject_set_has_new_constructor(VTE_TYPE_TERMINAL);. After this the reportet problem was solved. But then I get a new error message: Traceback (most recent call last):
symbol: pygobject_constructv And for this I haven't any idea how to change this.
Please try the latest vte release. This should be fixed already.
If 0.11.15 the latest then it isn't working again. On ftp://ftp.gnome.org/pub/gnome/sources/vte/0.11/ is 0.11.15 the latest. I get always the same error. Traceback (most recent call last):
+ Trace 62666
symbol: pyg_set_object_has_new_constructor
I don't see this error here. import vte works just fine here it seems. I have python-2.4.1 and pygtk2-2.7.3. Could it be that there's a missing build time dependency on some gnome-python package? Which of those do you have installed?
Okay, after one hour I have found the problem. I have now installed pygtk 2.7.4 and recompiled vte with this pygtk. Before I have do this I have pygtk 2.6.2 installed.
Johan, can you think of anything that could have caused the above problem?
I'm going to close this as a problem with a specific pygtk release. It's working for Marcus with 2.6.x and for me with 2.8.0, so maybe this was just a problem in a development release of pygtk?
Almost. It was a problem with pygtk 2.6.2 and solved with 2.7.4. :) Because the current pygtk (2.8.0) is working too, this bug can be closed.
Hey, I'm worried about this bug: I'm still experiencing it with python-vte 0.11.15 and pygtk 2.8.2. Please note that this is with Python 2.3, could it be the explanation of these problems? I tried rebuilding the latest python bindings for vte with Python 2.4, and it started working, hence I'm reopening this bug. What commitment do you make to versions of Python supported? Shouldn't this be checked at build time? (I'm also interested in any patch against pygtk 2.6.3 to fix this with Python 2.3.) Cheers,
*** Bug 316457 has been marked as a duplicate of this bug. ***
The problem is that python/vte.c was generated using pygtk 2.8. generating it with pygtk 2.6 helps going further, but still fails, see also bug 320931.
I confirm regenerating python/vte.c with pygtk 2.6 or simply removing it solves the problem, and I'm closing this bug. *** This bug has been marked as a duplicate of 320931 ***