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 pakal
Recipients Gregory.Salvan, Julian, eric.araujo, martin.panter, michael.foord, ncoghlan, pakal, r.david.murray, rbcollins, serhiy.storchaka
Date 2019-06-13.09:50:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I don't get it, why would failureException block anything ? The unittest.TestCase API must remain the same anyway, but it could become just a wrapper towards external assertions.

For example :

class TestCase:

   assertEqual = wrap(assertions.assert_equal)

Where "wrap" for example is some kind of functools.partial() injecting into external assertions a parameter "failure_exception_class". Having all these external assertions take such a parameter (defaulting to AssertionError) would be a great plus for adaptability anyway.
Date User Action Args
2019-06-13 09:50:01pakalsetrecipients: + pakal, ncoghlan, rbcollins, eric.araujo, r.david.murray, michael.foord, Julian, martin.panter, serhiy.storchaka, Gregory.Salvan
2019-06-13 09:50:01pakalsetmessageid: <>
2019-06-13 09:50:01pakallinkissue19645 messages
2019-06-13 09:50:01pakalcreate