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 michael.foord
Recipients BreamoreBoy, eric.araujo, kristjan.jonsson, michael.foord, pitrou, r.david.murray, serhiy.storchaka, stutzbach, zach.ware
Date 2014-06-18.10:23:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
To be honest, even though I understand it, I find the mixin pattern hard to read. You derive from object, but call methods (the assert methods for example) that don't exist in the class (or its inheritance chain).

My experience, with even experienced Python devs, is that they don't *properly* understand how to create mixins and they *much prefer* to write base classes that derive directly from TestCase. And then you have the problem that this issue is intended to resolve (and that we even have in the Python test suite).
Date User Action Args
2014-06-18 10:23:10michael.foordsetrecipients: + michael.foord, pitrou, kristjan.jonsson, stutzbach, eric.araujo, r.david.murray, BreamoreBoy, zach.ware, serhiy.storchaka
2014-06-18 10:23:10michael.foordsetmessageid: <>
2014-06-18 10:23:09michael.foordlinkissue14534 messages
2014-06-18 10:23:09michael.foordcreate