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 chris.jerdonek
Recipients Julian, Yaroslav.Halchenko, abingham, bfroehle, borja.ruiz, brian.curtin, chris.jerdonek, eric.araujo, eric.snow, exarkun, ezio.melotti, fperez, hpk, kynan, michael.foord, nchauvat, ncoghlan, pitrou, r.david.murray, santoso.wijaya, serhiy.storchaka, spiv
Date 2013-01-19.07:31:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAOTb1wfvdGqsMxcJ64EHf6MTcwtcAhJ58e6T1RXPxNbMvz-cMA@mail.gmail.com>
In-reply-to <1358556573.3462.7.camel@localhost.localdomain>
Content
Either way, something isn't right about how it's integrated now.  With
the patch, this:

    @unittest.expectedFailure
    def test(self):
        with self.subTest():
            self.assertEqual(0, 1)

gives: FAILED (failures=1, unexpected successes=1)

And this:

    @unittest.expectedFailure
    def test(self):
        with self.subTest():
            self.assertEqual(0, 0)

gives: OK (unexpected successes=1)

But without the patch, this:

    @unittest.expectedFailure
    def test(self):
        self.assertEqual(0, 1)

gives: OK (expected failures=1)
History
Date User Action Args
2013-01-19 07:31:32chris.jerdoneksetrecipients: + chris.jerdonek, spiv, exarkun, ncoghlan, pitrou, ezio.melotti, eric.araujo, r.david.murray, michael.foord, brian.curtin, hpk, fperez, Yaroslav.Halchenko, santoso.wijaya, nchauvat, kynan, Julian, abingham, eric.snow, serhiy.storchaka, borja.ruiz, bfroehle
2013-01-19 07:31:32chris.jerdoneklinkissue16997 messages
2013-01-19 07:31:31chris.jerdonekcreate