[Python-Dev] new failing test -- test_compiler

Jeremy Hylton jhylton at gmail.com
Sun Aug 8 16:26:33 CEST 2004


On Sat, 7 Aug 2004 20:35:44 -0400, Tim Peters <tim.peters at gmail.com> wrote:
> [Armin Rigo]
> > ...
> > This is now fixed by skipping the optimization if we got an interned string.
> > While messing with ob_refcnt is always a bit fragile I am still convinced that
> > the += optimization is safe again.
> 
> Ya, this bug wasn't scary (an unlikely but clear-in-hindsight problem,
> specifically due to a subsystem lying about true refcounts -- not much
> of that goes on, thank God).
> 
> Alas, test_compiler still fails (but in an ordinary "doesn't work"
> way, no longer in an internal-error way), so testing with -uall is
> still a bit broken.

I won't be able to fix it today, but I'll get on that asap.

Jeremy


More information about the Python-Dev mailing list