Steve Purcell added the comment: I guess I don't completely agree with the rationale, because I've never wanted this feature; when running tests en-masse after refactoring, I want an overview of what was broken. If the codebase is in good shape, the test failures will be few and close together, and then I can usually re-run one of the individual test cases to debug the error.
However, this isn't a big issue for me, and if someone's willing to prepare a new patch with the different implementation I described previously, I'm happy to re-open this ticket and sign off on it. I'd suggest using the same argument names as nose and py.test in this case. __________________________________ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2241> __________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
