Thanks for submission. I guess this bug happens due to argparse option processing: it finds arguments which follow after --megatest to get list of modules. If any other argument follows after --megatest, argparse thinks that everything what follow after such argument relies to it. To be honest, I don't know how to fix it with argparse; I guess that we could use just sys.argv, but it can make life harder. I need some time to fix it the proper way.
2012/9/21 Stefano Lattarini
<address@hidden>
Hello gnulibers.
I've found an incompatibility with between mainline gnulib-tool and
gnulib-tool.py. With mainline gnulib-tool, the following:
./gnulib-tool --megatest --with-tests y0 yn
works as expected, testingthe y0 and yn modules first separately and
then in combination. But with gnulib-tool.py:
$ python ./gnulib-tool.py --megatest --with-tests y0 yn
usage: gnulib-tool.py --help
./gnulib-tool.py: error: unrecognized arguments: y0 yn
I've not investigated further.
Regards,
Stefano
--
With best regards,
Dmitriy Selyutin
Phone: +7(985)334-07-70