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 purcell
Recipients amaury.forgeotdarc, bcwhite, purcell
Date 2008-03-06.14:15:28
SpamBayes Score 0.031165946
Marked as misclassified No
Message-id <1204812929.81.0.86993471295.issue2241@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2008-03-06 14:15:29purcellsetspambayes_score: 0.0311659 -> 0.031165946
recipients: + purcell, amaury.forgeotdarc, bcwhite
2008-03-06 14:15:29purcellsetspambayes_score: 0.0311659 -> 0.0311659
messageid: <1204812929.81.0.86993471295.issue2241@psf.upfronthosting.co.za>
2008-03-06 14:15:28purcelllinkissue2241 messages
2008-03-06 14:15:28purcellcreate