On Mon, 26 Jun 2017 at 13:38 Victor Stinner <victor.stin...@gmail.com> wrote:
> 2017-06-26 21:58 GMT+02:00 Brett Cannon <br...@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@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 ;-) > Then I think you answered your own question about whether this should go into regrtest ;) (Unless you want to rewrite regrtest's CLI to support subcommands.)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
