[issue24166] ArgumentParser behavior does not match generated help

2015-07-09 Thread Benjamin Schubert
Benjamin Schubert added the comment: Ok, sorry for the delay. I see your point and understand the difficulty of having done right. Should I close the issue, or propose something else ? Thanks -- ___ Python tracker <http://bugs.python.

[issue24166] ArgumentParser behavior does not match generated help

2015-05-12 Thread Benjamin Schubert
Benjamin Schubert added the comment: I solved my problem by subclassing the ArgumentParser and redefining parse_args as follow : class MultipleArgumentParser(ArgumentParser): def parse_args(self, args=None, namespace=None): args, argv = self.parse_known_args(args, namespace

[issue24166] ArgumentParser behavior does not match generated help

2015-05-12 Thread Benjamin Schubert
Benjamin Schubert added the comment: Thanks a lot for this explanation ! It is more clear now for why it is not working. However, I would suggest that the ArgumentParser should still try to match anything the subparser could not, or would this be too complicated ? Moreover, if this scheme is

[issue24166] ArgumentParser behavior does not match generated help

2015-05-11 Thread Benjamin Schubert
New submission from Benjamin Schubert: When creating a ArgumentParser on which we attach a subparser with different options and then add a nargs="+" argument to the initial parser, the command format string generated does not match the behavior. for example it woul