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 michael.foord, ncoghlan
Date 2013-05-28.09:44:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1369734275.94.0.87758804406.issue18054@psf.upfronthosting.co.za>
In-reply-to
Content
I'm slightly torn. 

TestCase has a wide (waaaay too wide) API and adding methods makes it wider. The use cases for these methods are relatively niche, so my instinct would be that these don't meet the bar for inclusion on TestCase.

On the other hand, despite their brevity they're hard to get right, so having them in the standard library is helpful from that point of view.

I might be more sympathetic to having some helper mixin classes, so that we can provide esoteric-but-difficult assert methods without having to dump them all on TestCase.
History
Date User Action Args
2013-05-28 09:44:36michael.foordsetrecipients: + michael.foord, ncoghlan
2013-05-28 09:44:35michael.foordsetmessageid: <1369734275.94.0.87758804406.issue18054@psf.upfronthosting.co.za>
2013-05-28 09:44:35michael.foordlinkissue18054 messages
2013-05-28 09:44:35michael.foordcreate