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/bisect_test.py --help > usage: bisect_test.py [-h] [-i INPUT] [-o OUTPUT] [-n MAX_TESTS] [-N MAX_ITER] > > 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 MAX_TESTS, --max-tests MAX_TESTS > Maximum number of tests to stop the bisection > (default: 1) > -N MAX_ITER, --max-iter MAX_ITER > 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
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