[Python-Dev] New work-in-progress bisection tool for the Python test suite (in regrtest) (original) (raw)
Serhiy Storchaka storchaka at gmail.com
Tue Jun 27 01:33:34 EDT 2017
- Previous message (by thread): [Python-Dev] New work-in-progress bisection tool for the Python test suite (in regrtest)
- Next message (by thread): [Python-Dev] New work-in-progress bisection tool for the Python test suite (in regrtest)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
26.06.17 23:37, Victor Stinner пише:
2017-06-26 21:58 GMT+02:00 Brett Cannon <brett at python.org>:
I don't see why regrtest isn't the right place for this. The current regrest CLI isn't designed for subcommands, and I don't want to "pollute" regrtest with multiple options for bisect. Currently, my script has already 4 options: haypo at selma$ python3 ~/prog/GIT/misc/python/bisecttest.py --help usage: bisecttest.py [-h] [-i INPUT] [-o OUTPUT] [-n MAXTESTS] [-N MAXITER] optional arguments: -h, --help show this help message and exit -i INPUT, --input INPUT Test names produced by --list-tests written into a file. If not set, run --list-tests -o OUTPUT, --output OUTPUT Result of the bisection -n MAXTESTS, --max-tests MAXTESTS Maximum number of tests to stop the bisection (default: 1) -N MAXITER, --max-iter MAXITER Maximum number of bisection iterations (default: 100) I really like subcommands, it's a nice way to design complex CLI ;-)
You could make it just a submodule in the test package.
./python -m test.bisect -R 3:3 test_os- Previous message (by thread): [Python-Dev] New work-in-progress bisection tool for the Python test suite (in regrtest)
- Next message (by thread): [Python-Dev] New work-in-progress bisection tool for the Python test suite (in regrtest)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]