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 belopolsky
Recipients Alexander.Belopolsky, amaury.forgeotdarc, belopolsky, eli.bendersky, ezio.melotti, flox, georg.brandl, pitrou, rhettinger, teresap989, terry.reedy
Date 2010-09-15.19:45:03
SpamBayes Score 3.9978957e-07
Marked as misclassified No
Message-id <1284579907.2.0.574767481256.issue9315@psf.upfronthosting.co.za>
In-reply-to
Content
Raymond asked on IRC why this work is being back-ported.  The answer is that it is being forward-ported rather than back-ported.  The trace module had no unittests in either 2.x or 3.x and was very buggy in 3.x.  Presumably, 2.x version saw more use and was likely to be more correct than 3.x, so we decided to start with adding unit tests to 2.7 and then port the tests to 3.x while fixing the bugs.  See msg111134.

This does not necessarily mean that we need to include 3.1. It may be appropriate to limit what is going to 3.1 to tests that support bug fixes.

If nobody raises an objection, I am going to close this issue by removing list comprehension test from 3.1 and will open a separate "interpreter core" issue for line tracing inconsistencies.
History
Date User Action Args
2010-09-15 19:45:07belopolskysetrecipients: + belopolsky, georg.brandl, rhettinger, terry.reedy, amaury.forgeotdarc, pitrou, ezio.melotti, eli.bendersky, flox, Alexander.Belopolsky, teresap989
2010-09-15 19:45:07belopolskysetmessageid: <1284579907.2.0.574767481256.issue9315@psf.upfronthosting.co.za>
2010-09-15 19:45:05belopolskylinkissue9315 messages
2010-09-15 19:45:03belopolskycreate