undefined symbol: PyUnicodeUCS4_FromEncodedObject

Jeffrey Barish jeff_barish at earthlink.net
Fri Oct 27 10:20:25 PDT 2006


F. Oliver Gathmann wrote:

> I had the same problem on SuSE 10.0. My workaround was to compile Python
> with wide unicode support - i.e., passing --enable-unicode=ucs4 to the
> Python configure script.

I tried what you suggested.  Much to my amazement, I was able to compile a
new Python with little difficulty.  However, before running make install, I
figured that I should remove the Python that was already on the system.  On
Ubuntu, removing Python (using apt) removes most of the OS.  I spent all
day yesterday reinstalling the OS.  This time I figured I better ask first. 
Where does make install put the new Python?  If it puts the new Python
in /usr/local/bin (and does not pollute either /usr/bin or /usr/lib) then I
suppose that I could operate my system with two Pythons, but that solution
seems clumsy.  Does anyone know whether there is a way to upgrade the
Python on Ubuntu to wide unicode support?  Is there a wxPython package that
does not require wide unicode support?  I see that there are both ansi- and
unicode-based packages for three RPM-based distributions.  How about
Debian?  I don't understand why there is a package in the Ubuntu repository
that does not run on the Python that ships with Ubuntu.  Other than this
problem, I like Ubuntu (Kubuntu, actually) so far.
-- 
Jeffrey Barish





More information about the wxpython-users mailing list