Description of problem: When importing wx: File "/home/schaerer/bin/Visu3D.py", line 5, in ? from wxPython.wx import * File "/usr/lib/python2.4/site-packages/wxPython/__init__.py", line 20, in ? import wxc ImportError: /usr/lib/libwx_gtk2-2.4.so.0: undefined symbol: pango_x_get_context Version-Release number of selected component (if applicable): wxPythonGTK2 i386 2.4.2.4-7 extras 4.7 M compat-wxGTK2 i386 2.4.2-17.fc5 extras 1.7 M compat-wxGTK2-gl i386 2.4.2-17.fc5 extras 19 k How reproducible: Always Steps to Reproduce: 1. Import wxPython.wx 2. watch crash 3.
This is known and in-progress. Can't realistically work on it until after fudcon, though -- sorry. But I know a lot of people are depending on this so it _will_ get done soon. *** This bug has been marked as a duplicate of 163440 ***
Bug number 163440 has been closed, but the problem is still there. I upgraded to the latest version in fc5, that is: compat-wxPythonGTK2-2.4.2.4-11.fc5 and I get the same bug: Traceback (most recent call last): File "/usr/lib/DaVaW/DaVaW/demo/demo.py", line 25, in ? from wxPython.wx import * File "/usr/lib/python2.4/site-packages/wxPython/__init__.py", line 20, in ? import wxc ImportError: /usr/lib/libwx_gtk2-2.4.so.0: undefined symbol: pango_x_get_context So I'm reopening the bug, I hope it's the right thing to do?
The latest version of wxPython 2.4.x is compat-wxPythonGTK2-2.4.2.4-11.fc5, but unless you specifically need the old version (which is not maintained upstream), it is recommended that you use the new wxPython 2.6.x package instead. The specific bit that's failing there -- just importing things -- should work fine. It's possible that something else in the code is incompatible, though. Have you tested that?
I'm not sure what you're asking, but yes, I specifically need wxPython 2.4. I'm trying to run a library that hasn't been ported to the latest wxPython yet. Since something so simple as the import fails, I suppose there is something wrong with the package. Have you tested it?
Yeah, it's a Known Thing that the 2.4.x compat package is broken. See bug #185777. In fact, I'm going to mark this as a dup of that. I hadn't actually tried installing the compat package before, so this is the first that I noticed that installing that breaks *everything*. Urgh. *** This bug has been marked as a duplicate of 185777 ***