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 eric.araujo
Recipients eric.araujo, ezio.melotti, michael.foord, r.david.murray
Date 2011-06-10.16:56:22
SpamBayes Score 1.5078884e-07
Marked as misclassified No
Message-id <1307724983.43.0.0599783418108.issue12314@psf.upfronthosting.co.za>
In-reply-to
Content
> maybe there's some way to reuse unittest's assertEqual machinery?
Hum, I think the diff functionality is cleanly separated in a (private) method, so we could get diff for free.

> I also wonder if the whole environment-changed thing should be moved
> into unittest so it could wrap around individual test methods.
Yeah, I was thinking about a WatchfulTestRunner that would perform the same checks.  It annoys me to have two diverging sets of features to run tests: either checks with regrtest, or failfast, discovery and granularity with unittest.
History
Date User Action Args
2011-06-10 16:56:23eric.araujosetrecipients: + eric.araujo, ezio.melotti, r.david.murray, michael.foord
2011-06-10 16:56:23eric.araujosetmessageid: <1307724983.43.0.0599783418108.issue12314@psf.upfronthosting.co.za>
2011-06-10 16:56:22eric.araujolinkissue12314 messages
2011-06-10 16:56:22eric.araujocreate