On 03/03/2011 20:31, anatoly techtonik wrote: > I am looking at --help of test runner and asking the question: what is > the use case for -c, --catch option? It catches keyboard interrupt and instead of just bombing out of the test run it reports all the results collected so far. Without this option interrupting a test run with a ctrl-c kills the run and reports nothing. Seeing an unexpected failure or error during a long test run and having to wait to the end of the test run to see the traceback can be annoying, this feature solves that problem. > It doesn't look like it should be > present in generic runner. I also can't find reasons to waste short > option for it. Nose, django and other test runners provide this option, so it is functionality that people seem to value. > There will be big problems with people complaining > about BC break even if this option is not used by anyone. > I don't understand this sentence, sorry. All the best, Michael Foord > Usage: tests.py [options] [test] [...] > > Options: > -h, --help Show this message > -v, --verbose Verbose output > -q, --quiet Minimal output > -f, --failfast Stop on first failure > -c, --catch Catch control-C and display results > -b, --buffer Buffer stdout and stderr during test runs > > > -- > anatoly t. > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk -- http://www.voidspace.org.uk/ May you do good and not evil May you find forgiveness for yourself and forgive others May you share freely, never taking more than you give. -- the sqlite blessing http://www.sqlite.org/different.html
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4