break unichr instead of fix ord?
rurpy at yahoo.com
rurpy at yahoo.com
Wed Aug 26 19:35:51 EDT 2009
On Aug 26, 2:05 am, Vlastimil Brom <vlastimil.b... at gmail.com> wrote:
>[...]
> Hi,
> I'm not sure about the exact reasons for this behaviour on narrow
> builds either (maybe the consistency of the input/ output data to
> exactly one character?).
>
> However, if I need these functions for higher unicode planes, the
> following rather hackish replacements seem to work. I presume, there
> might be smarter ways of dealing with this, but anyway...
>
> hth,
> vbr
>
>[...code snipped...]
Thanks, I wrote a replacement ord function nearly identical
to yours but will steal your unichr function if that's ok. :-)
But I still wonder why all this is neccessary.
More information about the Python-list
mailing list