The RPM releases of wxPython 2.5 that use GTK2 also use Unicode.
Is this a requirement of GTK2 or just because you didn't want
to have yet another set of variations (GTK1 vs 2, plain vs Unicode, py 2.2 vs 2.3, RH9 vs FC2)
Roger
Roger Binns wrote:
The RPM releases of wxPython 2.5 that use GTK2 also use Unicode.
Is this a requirement of GTK2 or just because you didn't want
to have yet another set of variations (GTK1 vs 2, plain vs Unicode, py 2.2 vs 2.3, RH9 vs FC2)
Basically. wxGTK2 can be built for either ansi or unicode, but GTK 2.x uses all UTF-8 internally and so doing just unicode builds seems to make the most sense to me. You should be able to build the ansi version yourself if that is what you want.
ยทยทยท
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
Basically. wxGTK2 can be built for either ansi or unicode, but GTK 2.x uses all UTF-8 internally and so doing just unicode builds seems to make the most sense to me. You should be able to build the ansi version yourself if that is what you want.
I am trying to avoid doing my own builds, although rpmbuild --rebuild
works well, even on Gentoo. I managed to do all the code changes for
the 2.4 to 2.5 for BitPim in 3 hours. Unfortunately there is some
nasty bug in the html and custom tag handling that then coredumps
stuff which I am trying to track down.
I wanted to move to GTK2 first and then worry about Unicode. Unfortunately
Python is very Unicode hostile. For example I get some strings
that have been through wxPython, and then use a dict of them as
a keyword arg to a function and Python doesn't like the
keyword names to be unicode strings, even though they are actually just ascii characters ("width" and "height"). It
will take a little while to fix and find all those places.
So I have resorted to doing GTK1 first and then moving to
GTK2 and Unicode.
Roger