[Python-3000] Lazy strings (was Re: Py3k release schedule worries)
Josiah Carlson
jcarlson at uci.edu
Fri Jan 12 18:29:55 CET 2007
"Guido van Rossum" <guido at python.org> wrote:
> On 1/11/07, Larry Hastings <larry at hastings.org> wrote:
> > It applies cleanly (with "patch -p1") against the current revision of
> > the Py3k branch, #53392. The resulting tree builds as cleanly as an
> > unpatched Py3k, on both Win32 and Linux, and the output from the
> > regression tests is also unchanged.
> >
> > As discussed on that page, the current version of the patch could cause
> > crashes in low-memory conditions. I welcome suggestions on how best to
> > resolve this problem. Apart from that fly in the ointment I'm pretty
> > happy with how it all turned out.
>
> What kind of crashes? The right thing to do is to raise MemoryError.
> Is there anything besides sheer will power that prevents that?
It may require changing around 400 uses of the PyUnicode_AS_UNICODE
macro in the trunk to allow the return of a NULL (which the current
semantics don't allow). Any 3rd party code using the macro would also
need to be changed.
- Josiah
More information about the Python-3000
mailing list