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 r.david.murray
Recipients eli.bendersky, ezio.melotti, georg.brandl, ncoghlan, python-dev, r.david.murray, vlad
Date 2013-09-13.14:31:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If they are part of a bug fix, then sure.  That wasn't clear from this issue, though.  On the other hand, if the tests in that other issue cover the actual bug, and these have any chance of *introducing* test failures (especially if they are heisenburgs, although I'm assuming the point is that they are not), then I'd say no.  The issue with backporting tests isn't about "maintenance burden" (backporting tests actually makes the maintenance burden smaller, not larger).  The issue is potential effectively spurious test failures in the field in a maintenance release.

To put it another way: the right place to find test bugs is in a feature release, which we then fix in the next maintenance release.  We do *not* want to find test bugs in maintenance releases.
Date User Action Args
2013-09-13 14:31:51r.david.murraysetrecipients: + r.david.murray, georg.brandl, ncoghlan, ezio.melotti, eli.bendersky, python-dev, vlad
2013-09-13 14:31:51r.david.murraysetmessageid: <>
2013-09-13 14:31:51r.david.murraylinkissue18945 messages
2013-09-13 14:31:50r.david.murraycreate