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 georg.brandl, michael.foord
Date 2009-05-05.23:00:07
SpamBayes Score 4.633127e-12
Marked as misclassified No
Message-id <1241564409.11.0.779371397916.issue5846@psf.upfronthosting.co.za>
In-reply-to
Content
So it turns out that unittest.makeSuite is used about 100 times
throughout the standard library tests.

More than half the time it can be replaced with
unittest.TestLoader().loadTestsFromTestCase(...)

Some of the other times a loader needs to be constructed and then a
testMethodPrefix of 'Check' set (yuck!).

I'm about halfway through a patch that does this. Think it is worth
continuing or shall I drop it. I don't mind doing it so long as
*someone* thinks it is worthwhile... :-)

(I haven't yet checked for getTestCaseNames but I imagine there will be
a bunch of these to fix as well.)

Another possibility is to move the functions into test_support
(deprecating first) where at least they are out of unittest.
History
Date User Action Args
2009-05-05 23:00:09michael.foordsetrecipients: + michael.foord, georg.brandl
2009-05-05 23:00:09michael.foordsetmessageid: <1241564409.11.0.779371397916.issue5846@psf.upfronthosting.co.za>
2009-05-05 23:00:08michael.foordlinkissue5846 messages
2009-05-05 23:00:07michael.foordcreate