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 ncoghlan
Recipients Julian, aliles, ezio.melotti, michael.foord, ncoghlan, rhettinger, serhiy.storchaka
Date 2013-06-04.08:49:52
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1370335792.97.0.263492659915.issue18054@psf.upfronthosting.co.za>
In-reply-to
Content
I like the idea of using the strategy pattern to at least decouple the assertion API from the main testcase API. I also like it better than the mixin suggested earlier.

We would obviously have to keep the existing methods for backwards compatibility, but could avoid adding new ones.

I'm not sure what such an API would look like, though :(
History
Date User Action Args
2013-06-04 08:49:53ncoghlansetrecipients: + ncoghlan, rhettinger, ezio.melotti, michael.foord, Julian, aliles, serhiy.storchaka
2013-06-04 08:49:52ncoghlansetmessageid: <1370335792.97.0.263492659915.issue18054@psf.upfronthosting.co.za>
2013-06-04 08:49:52ncoghlanlinkissue18054 messages
2013-06-04 08:49:52ncoghlancreate