[issue34191] argparse: Missing subparser error message should be more clear

Change by Ned Deily : -- resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> argparse fails with required subparsers, un-named dest, and empty argv ___ Python tracker ___

[issue34191] argparse: Missing subparser error message should be more clear

Jacob Walls added the comment: Duplicate of issue29298 (fixed) -- nosy: +jacobtylerwalls ___ Python tracker ___ ___ Python-bugs-lis

[issue34191] argparse: Missing subparser error message should be more clear

paul j3 added the comment: Updating you Python3.7 might change the behavior. If I read https://github.com/python/cpython/commits/master/Lib/argparse.py correctly, subparsers are no longer required by default (it reverted back to earlier Py3 behavior). There is a proposed patch for handling

[issue34191] argparse: Missing subparser error message should be more clear

paul j3 added the comment: Your code runs fine under 3.6.5. But if I add 'subparsers.required=True', I get your error. It's having problems formatting the name of the subparsers command when issuing the error message. If I add a 'dest' to the add_subparsers I get the expected error message

[issue34191] argparse: Missing subparser error message should be more clear

New submission from Victor Porton : argparse produces a long unreadable, non-understandable for non-programmers error message when a subparser is not specified in the command line. Note that the below message contains Ubuntu specifics, but it seems it would be nearly as unclear on other OSes