Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #49355 > unrolled thread

Re: Why is the argparse module so inflexible?

Started byOscar Benjamin <oscar.j.benjamin@gmail.com>
First post2013-06-28 01:23 +0100
Last post2013-06-28 01:23 +0100
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Why is the argparse module so inflexible? Oscar Benjamin <oscar.j.benjamin@gmail.com> - 2013-06-28 01:23 +0100

#49355 — Re: Why is the argparse module so inflexible?

FromOscar Benjamin <oscar.j.benjamin@gmail.com>
Date2013-06-28 01:23 +0100
SubjectRe: Why is the argparse module so inflexible?
Message-ID<mailman.3947.1372379054.3114.python-list@python.org>
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

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web