[Python-Dev] 2.2.1 issues

Martin v. Loewis martin@v.loewis.de
19 Feb 2002 21:29:49 +0100

"M.-A. Lemburg" <mal@lemburg.com> writes:

> Right. 1) was caused by 2).

That wasn't actually the case. The overwriting of memory was really
independent of the error in surrogate processing, and can be fixed

> As a result, modules using unpaired surrogates in Unicode
> literals are simply broken in Python <= 2.2.0.

I think this is unimportant enough to just accept this bug for Python
2.2.x. If people ever run into the problem, well: just don't do this.
Unpaired surrogates will be entirely in Unicode 3.2.

> The problem with backporting this patch is that in order
> for Python to properly recompile any broken module, the
> magic will have to be changed. Question is whether this
> is a reasonable thing to do in a patch level release...

The memory-overwriting problem can be fixed independently, e.g. with