[issue8074] Fail-fast behavior for unittest

Michael Foord added the comment: Ctrl-C handling now implemented (-c command line option). Still needs documentation, but there is a bunch of this outstanding and I will do it in one go and rework the unittest docs at the same time. -- stage: needs patch -> committed/rejected status:

[issue8074] Fail-fast behavior for unittest

Michael Foord added the comment: Failfast option added, committed revision 79265. Still needs documentation. Ctrl-C handling not yet done. Slightly more complex as it needs to play well with tests that test SIGINT handling. -- resolution: -> accepted

[issue8074] Fail-fast behavior for unittest

Michael Foord added the comment: I like the feature. I'm a bit concerned about the proliferation of command line options for unittest though. Steve's rejection of the feature seemed to be on the basis that he didn't need it (or see a need for it). :-) -- ___

[issue8074] Fail-fast behavior for unittest

Amaury Forgeot d'Arc added the comment: fwiw, the similar issue2241 was rejected two years ago. -- nosy: +amaury.forgeotdarc ___ Python tracker ___ __

[issue8074] Fail-fast behavior for unittest

Changes by Brian Curtin : -- assignee: -> michael.foord nosy: +michael.foord priority: -> normal stage: -> needs patch versions: -Python 3.1, Python 3.3 ___ Python tracker ___

[issue8074] Fail-fast behavior for unittest

Cliff Dyer added the comment: This feature was implemented in the django test runner as [r12034](http://code.djangoproject.com/changeset/12034) (^C override) and [r11843](http://code.djangoproject.com/changeset/11843) (failfast option) -- ___ Pytho

[issue8074] Fail-fast behavior for unittest

New submission from Cliff Dyer : When a long suite of tests is running, it would be nice to be able to exit out early to see the results of the tests that have run so far. I would like to see a couple of features included in `unittest` to this effect that have recently been implemented in dj