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 r.david.murray
Recipients anacrolix, eric.araujo, michael.foord, r.david.murray
Date 2012-03-29.13:21:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I guess I'm not really done talking about this, though my bow to you as maintainer still stands.

The mixin tests *can't* be run in isolation, that's the whole point.  Otherwise you could just let unittest run them, and wouldn't need to mark them as not-really-a-TestCase.  The typical mixin test class uses attributes that don't exist except on the concrete TestCases, so I'm not sure why calling methods that don't exist on the mixin is any worse :)
Date User Action Args
2012-03-29 13:21:41r.david.murraysetrecipients: + r.david.murray, eric.araujo, michael.foord, anacrolix
2012-03-29 13:21:41r.david.murraysetmessageid: <>
2012-03-29 13:21:41r.david.murraylinkissue14408 messages
2012-03-29 13:21:41r.david.murraycreate