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 rbcollins
Recipients Gregory.Salvan, Julian, eric.araujo, martin.panter, michael.foord, ncoghlan, r.david.murray, rbcollins, serhiy.storchaka
Date 2019-06-13.08:59:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Sorry for the slow reply here;

There are API breaks involved in any decoupling that involves the exception raising because of the failureException attribute. Something with signalling that can be adapted by other test suites etc might have merit, but I think we are lacking a clear use case for doing this to the existing exceptions. Setting up a way for new things to be more easily used by users of other test frameworks is quite attractive; perhaps just writing them as separate functions with an adapter to failureException would be sufficient.
Date User Action Args
2019-06-13 08:59:39rbcollinssetrecipients: + rbcollins, ncoghlan, eric.araujo, r.david.murray, michael.foord, Julian, martin.panter, serhiy.storchaka, Gregory.Salvan
2019-06-13 08:59:39rbcollinssetmessageid: <>
2019-06-13 08:59:39rbcollinslinkissue19645 messages
2019-06-13 08:59:39rbcollinscreate