Matthew Knepley <knep...@gmail.com> writes:
> On Fri, Mar 2, 2018 at 6:17 PM, Scott Kruger <kru...@txcorp.com> wrote:
>> On 3/2/18 12:44 PM, Matthew Knepley wrote:
>>> On Fri, Mar 2, 2018 at 2:39 PM, Jed Brown <j...@jedbrown.org <mailto:
>>> j...@jedbrown.org>> wrote:
>>> Matthew Knepley <knep...@gmail.com <mailto:knep...@gmail.com>>
>>> > That is not the same as printing unused arguments. Michael's Pythia
>>> > does this correctly, but it is even less simple.
>>> You want it to accept the unused arguments and just print them without
>>> error, or some more subtle relationship among dependent options?
>>> Yes, I do. I consider PETSc to have the correct functionality. The open
>>> assumption is a good one, as long as you report that no one accepted that
>> Requires Python > 2.7
> Good catch!
I'm not sure it's quite what Matt is after. Argparse is in the standard
library since 2.7, but is available for earlier versions of Python.
> The other thing I remember argparse not doing last time I checked, was
> that it could group options into sections like we want for our help.
That has always been in argparse. Maybe you're thinking of some earlier
options parsing library.