Author paul.j3
Recipients bigbird, joshmeranda, mhughes, paul.j3, rhettinger, xtreak
Date 2021-09-11.05:39:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1631338747.04.0.134790583973.issue41255@roundup.psfhosted.org>
In-reply-to
Content
In

https://stackoverflow.com/questions/69108632/unable-to-catch-exception-error-for-argparse

it looked like `exit_on_error` does not work when using subparsers.  On on further thought, I realized that it has to included in the definition of the subparser.  As with other `ArgumentParser` parameters, the subparsers does not inherit from the main parser.  

So it's basically a documentation issue.  The `add_parser` method is described briefly as:

     which takes a command name and any ArgumentParser constructor 
     arguments, and returns an ArgumentParser object that can be 
     modified as usual.

But as my experience shows, its relevance is easily missed, even by an experienced users.
History
Date User Action Args
2021-09-11 05:39:07paul.j3setrecipients: + paul.j3, rhettinger, xtreak, mhughes, bigbird, joshmeranda
2021-09-11 05:39:07paul.j3setmessageid: <1631338747.04.0.134790583973.issue41255@roundup.psfhosted.org>
2021-09-11 05:39:07paul.j3linkissue41255 messages
2021-09-11 05:39:06paul.j3create