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 ezio.melotti, martin.panter, michael.foord, r.david.murray, rbcollins
Date 2015-01-01.16:06:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1420128396.96.0.971653839798.issue23142@psf.upfronthosting.co.za>
In-reply-to
Content
According to the docs, there's no reason to use FunctionTestCase unless you are dealing with legacy test code (eg: importing it from some existing module), so yes your "this seems easier" is certainly easier :)

(I wasn't even aware FunctionTestCase existed.)

I'm not sure what the issues would be with making them discoverable.  We'll wee what Robert and/or Michael have to say.
History
Date User Action Args
2015-01-01 16:06:36r.david.murraysetrecipients: + r.david.murray, rbcollins, ezio.melotti, michael.foord, martin.panter
2015-01-01 16:06:36r.david.murraysetmessageid: <1420128396.96.0.971653839798.issue23142@psf.upfronthosting.co.za>
2015-01-01 16:06:36r.david.murraylinkissue23142 messages
2015-01-01 16:06:36r.david.murraycreate