[issue21616] argparse explodes with nargs='*' and a tuple metavar

Change by Irit Katriel : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> argparse allows nargs>1 for positional arguments but doesn't allow metavar to be a tuple ___ Python tracker

[issue21616] argparse explodes with nargs='*' and a tuple metavar

Vasilis Vasaitis added the comment: Ah, I did come across that issue when I was searching for prior reports, but somehow it didn't register in my head as being the same thing. Does the fix for that address the behaviour I'm seeing too? If so, feel free to close as a duplicate. Additionally, if

[issue21616] argparse explodes with nargs='*' and a tuple metavar

paul j3 added the comment: I think is issue was already raised in http://bugs.python.org/issue14074 argparse allows nargs>1 for positional arguments but doesn't allow metavar to be a tuple -- nosy: +paul.j3 ___ Python tracker

[issue21616] argparse explodes with nargs='*' and a tuple metavar

New submission from Vasilis Vasaitis: The title says it all really, but to demostrate: Let's say I'm building a program which takes another command as its argument(s) on the command line, to execute it in a special way or whatever. The natural way to do this then would be something like the fo

[issue21616] argparse explodes with nargs='*' and a tuple metavar

Changes by Vasilis Vasaitis : -- versions: +Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://