➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients alex, amaury.forgeotdarc, benrg, brian.curtin, eric.araujo, georg.brandl, ishimoto, jackdied, jcea, loewis, meador.inge, mrabarnett, ncoghlan, pitrou, python-dev, r.david.murray, rhettinger, skrah, terry.reedy, tim.golden, vstinner
Date 2012-08-01.13:32:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <20120801153231.Horde.D-SVSklCcOxQGS-vQmBCQmA@webmail.df.eu>
In-reply-to <CAMpsgwaEAAKBJN6fdoiNX5DPV0Mk1BVSakvEV6iLW=UgPLV6eg@mail.gmail.com>
Content 
> Ah yes, you added new tests to Python 3.2 and 3.3, but no to Python
> 2.7. Why not adding these new tests to Python 2.7?

The tests don't crash Python 2.7. So they are not useful as a test whether
the bug has been worked-around. I actually don't know how to test this  
compiler
bug in Python 2.7 (except for writing specific C code that tries to trigger
the bug).
History
Date User Action Args
2012-08-01 13:32:32loewissetrecipients: + loewis, georg.brandl, rhettinger, terry.reedy, jcea, ishimoto, amaury.forgeotdarc, ncoghlan, pitrou, vstinner, jackdied, tim.golden, eric.araujo, mrabarnett, alex, r.david.murray, brian.curtin, skrah, meador.inge, benrg, python-dev
2012-08-01 13:32:32loewislinkissue8847 messages
2012-08-01 13:32:31loewiscreate