Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #49355
| References | (1 earlier) <kqhusi$je5$1@ger.gmane.org> <51CC8205.5060906@davea.name> <kqi0s8$a5d$1@ger.gmane.org> <51CC897E.5000702@stoneleaf.us> <CAEk9e3qrdPfW3rJaAGRUimUDa6o5mJp9ODA1fkroLQKopGUKRw@mail.gmail.com> |
|---|---|
| From | Oscar Benjamin <oscar.j.benjamin@gmail.com> |
| Date | 2013-06-28 01:23 +0100 |
| Subject | Re: Why is the argparse module so inflexible? |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.3947.1372379054.3114.python-list@python.org> (permalink) |
On 27 June 2013 22:30, Jason Swails <jason.swails@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
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Why is the argparse module so inflexible? Oscar Benjamin <oscar.j.benjamin@gmail.com> - 2013-06-28 01:23 +0100
csiph-web