[Python-Dev] new failing test -- test_compiler (original) (raw)
Tim Peters tim.peters at gmail.com
Sun Aug 8 02:35:44 CEST 2004
- Previous message: [Python-Dev] new failing test -- test_compiler
- Next message: [Python-Dev] new failing test -- test_compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Armin Rigo]
... This is now fixed by skipping the optimization if we got an interned string. While messing with obrefcnt 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.
- Previous message: [Python-Dev] new failing test -- test_compiler
- Next message: [Python-Dev] new failing test -- test_compiler
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]