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:28:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
(Redirected here from

I haven't dug the assertThat() idea, but why not make, as a first step, turn assertion methods in TestCase to staticmethods/classmethods, instead of instance methods?

Since they (to my knowledge) don't need to access an instance dict, they could be turned into such instance-less methods, and thus be usable from other testing frameworks (like pytest, for those who want to use pytest fixtures and yet benefit from advanced assertions like Django's TestCase's assertions).

"failureException" and others are meant to be (sub)class attributes, so no backwards incompatible change should occur (unless someone did really weird things with manually instantiated TestCases).
Date User Action Args
2019-06-13 09:28:55pakalsetrecipients: + pakal, ncoghlan, rbcollins, eric.araujo, r.david.murray, michael.foord, Julian, martin.panter, serhiy.storchaka, Gregory.Salvan
2019-06-13 09:28:55pakalsetmessageid: <>
2019-06-13 09:28:55pakallinkissue19645 messages
2019-06-13 09:28:55pakalcreate