[patch] nose.tools should use unittest2 if available

[jpellerin]

As the summary says, if unittest2 is available, its assertions should be used.

I have written a patch for this here: http://code.google.com/r/wolever-python-nose-unittest2/source/detail?r=d4d0c62184e710d2fe3712ea8845b1f1fb709e9e

Given that unittest2 claims to be 100% backwards compatible, I don't believe this will create any backwards compatibility problems.

The biggest issue I can see it causing would be if a developer unknowingly uses unittest2 assertions, then another developer without unittest2 runs the tests. They would get an incredibly unhelpful cannot import name assert_in.

I have started to use this patch in my projects, and it seems to work there (although there hasn't been enough time to be sure).

Google Code Info:
Issue #: 392
Author: [email protected]
Created On: 2011-01-16T07:34:31.000Z
Closed On:

[wolever]

If I submit a pull request for this, will it be accepted?

[jpellerin]

Seems like a reasonable change to me, thought ideally I'd like to see it tested somehow (maybe a separate tox config?)

Edit: to answer your actual question :) more clearly, a pull request here would get this to the top of the patch queue and would increase the chances of it being accepted soon by a lot.