Frank:
Many thanks for your message. I thought I had used Google enough, but did not run into this. It appears to work. Well, at least I can import wxPython.wx without error messages.
With Python 2.4.1 source from python.org on FC3 I am using:
make clean
./configure --prefix=/usr --enable-unicode=ucs4
make
make test
make install
Is there anything else that I should add? I wish it were possible to get the rpm install to recognize the location of Python. Now I see why someone suggested building wxPython from source. The install might have recognized the location of my Python.
···
-------Original Message-------
From: Frank Millman <frank@chagford.com>
Subject: RE: [wxPython-users] Installation of multiple versions
Sent: 2005-07-19 03:24Paul Watson wrote:
>I built Python 2.4.1 from source on FC3. It installed into
>/usr/local/lib/python24.[snip]
>I can manually add the wxPython location to sys.path, but I end up with a
>missing symbol, 'PyUnicodeUCS4_FromEncodedObject'.Here is a message I posted on 2nd May, together with Robin's reply -
--------------------------------------------------------
> Hi all
>
> I took a spare hard drive, cleared it, and installed FC3. Then I
> installed Python 2.4.1 - the only tweak I gave it was 'prefix=/usr'.
> Then I installed the rpm's for wxPython 2.6.0-gtk2-unicode-fc2 (there is
no version for fc3).
> It seemed to install ok, but if I try to import wx, I get an error to
> do with 'PyUnicodeUCS4_FromEncodedObject'.
>
> I did some investigation, and found the following in the Python
> installation README -
>
> 'Red Hat 9 built Python2.2 in UCS-4 mode and hacked Tcl to support it.
> To compile Python with Tkinter on these systems, you will need to pass
> --enable-unicode=ucs4 flag to ./configure. This is no longer needed in
> Fedora code'.Yep, the Python 2.4 I used for the builds comes from the source RPM on
python.org, and it is still using the ucs4 configure flag. If that is not
how the default Python is build on Fedora any longer I guess I should change
that and do a custom build of Python for the build machines.>
> Using this as a clue, I cleared everything and started the installation
> again, and passed this flag when compiling Python. Now when I import wx,
it works correctly.
>
> I am fairly sure that if I started again, compiled Python without using
> this flag, and compiled wxPython from source, it would work correctly.
> Is it worth my while doing this, or is it ok to carry on with the way I
> have installed it?It should be ok in either build mode. The only difference is that each
unicode character is 32 bits instead of 16 and you can then get to the
supplementary character planes without encoding.Robin Dunn
--------------------------------------------------------
HTH
Frank Millman
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org
-------Original Message-------