Why is the argparse module so inflexible?

[Oscar Benjamin]

On 27 June 2013 22:30, Jason Swails <jason.swails at gmail.com> wrote:
>
> An alternative is, of course, to simply subclass ArgumentParser and copy
> over all of the code that catches an ArgumentError to eliminate the internal
> exception handling and instead allow them to propagate the call stack.

I would think it easier to wrap getopt than monkey-patch argparse in this way.


Oscar