[Python-Dev] unicodeobject.c,2.139,2.140 checkin (original) (raw)

Tim Peters tim.one@comcast.net
Thu, 25 Apr 2002 18:25:33 -0400

[M.-A. Lemburg]

I don't know why it is, but Unicode always seems to unnecessarily heat up any discussion involving it.

Huh -- I thought I was the only one who noticed this .

I would really like to know what is causing this: is it a religious issue, does it have to do with the people involved or is Unicode inherently controversial ?

Unicode had nothing to do with my yelling in this thread. I've got very low tolerance for memory corruption, regardless of source. When it happens once I'm on high alert, when it happens twice in the same place I go postal. Had this been in dictobject.c or boolobject.c, I would have been just as unhappy.

Now that the memory corruption is thought to be solved, and verified in the debug build regardless, now I'll get cranky about foreigners and their lameass character sets .

On the technical issues remaining, I don't know how to judge the tradeoff between memory use and speed here. If you do, and pymalloc can help in some way, I'll be happy to help.