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 zach.ware
Recipients BreamoreBoy, eric.araujo, kristjan.jonsson, michael.foord, pitrou, r.david.murray, stutzbach, zach.ware
Date 2014-06-17.16:56:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1403024213.16.0.480902660928.issue14534@psf.upfronthosting.co.za>
In-reply-to
Content
What if we simply rename the current unittest.TestCase class to unittest.BaseTestCase, and define unittest.TestCase as "class TestCase(BaseTestCase): pass"?  Then mixin classes can derive from BaseTestCase and have all of the TestCase methods available (for auto-completion, etc.), but won't be picked up by discovery.  Real test classes would derive from TestCase as usual (but would still have to do so explicitly when also using a mixin), and all current code should work without modification.
History
Date User Action Args
2014-06-17 16:56:53zach.waresetrecipients: + zach.ware, pitrou, kristjan.jonsson, stutzbach, eric.araujo, r.david.murray, michael.foord, BreamoreBoy
2014-06-17 16:56:53zach.waresetmessageid: <1403024213.16.0.480902660928.issue14534@psf.upfronthosting.co.za>
2014-06-17 16:56:53zach.warelinkissue14534 messages
2014-06-17 16:56:52zach.warecreate