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, benjamin.peterson, georg.brandl, maker, python-dev, r.david.murray, rhettinger
Date 2012-03-17.20:49:39
SpamBayes Score 1.0857384e-05
Marked as misclassified No
Message-id <1332017380.77.0.963155117985.issue14333@psf.upfronthosting.co.za>
In-reply-to
Content
Not only do I think we should support calling our tests via unittest, I think we should move in the direction of having regrtest be implemented via standard unittest hooks rather than the monster it currently is.  That will take quite a bit of effort, though :)

Given that we are in fact using unittest, I think it is much clearer to follow the standard unittest pattern and have tests that are supposed to be run marked by subclassing TestCase, rather than by being explicitly nominated in boilerplate at the bottom.  Certainly any new test files I write work that way (and I even explicitly use test discovery in test_email).
History
Date User Action Args
2012-03-17 20:49:40r.david.murraysetrecipients: + r.david.murray, georg.brandl, rhettinger, benjamin.peterson, anacrolix, maker, python-dev
2012-03-17 20:49:40r.david.murraysetmessageid: <1332017380.77.0.963155117985.issue14333@psf.upfronthosting.co.za>
2012-03-17 20:49:40r.david.murraylinkissue14333 messages
2012-03-17 20:49:40r.david.murraycreate