Trond Eivind Glomsrød wrote:
> I am currently writing a python interface to a C++ library. Some of the
> functions in this library take unicode strings (UTF-8, mostly) as
> arguments.
>
> However, when getting these data I run into problem on python 2.2
> (RHEL3) - while the data is all nice UCS4
Python comes in two flavors. In one, sys.maxunicode is 65535 and Py_UNICODE is
a 16-bit type, and in the other, sys.maxunicode is 1114111 and Py_UNICODE is a
32-bit type. This is selected at compile time, and RedHat has chosen in some
versions to compile for sys.maxunicode == 1114111.
By using t
I am currently writing a python interface to a C++ library. Some of the
functions in this library take unicode strings (UTF-8, mostly) as arguments.
However, when getting these data I run into problem on python 2.2
(RHEL3) - while the data is all nice UCS4 in 2.3, in 2.2 it seems to be
UTF-8 o
