[Python-Dev] argparse ambiguity handling
Steven Bethard
steven.bethard at gmail.com
Tue Apr 20 21:10:00 CEST 2010
More information about the Python-Dev mailing list
Tue Apr 20 21:10:00 CEST 2010
- Previous message: [Python-Dev] argparse ambiguity handling
- Next message: [Python-Dev] argparse ambiguity handling
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Apr 20, 2010 at 11:55 AM, Neal Becker <ndbecker2 at gmail.com> wrote: > I've noticed argparse ambiguity handling has changed a bit over last few > revisions. > > I have cases where 1 valid input is a prefix of another: > > e.g.: > '--string' > '--string2' > > With the most recent 1.1, the behavior is: > > --string=hello > > is accepted, while: > > --strin=hello > > is marked as ambiguous. > > I'm OK with this, but just want to know if there is agreement that this is > the behavior we want. I don't have a strong feeling about this. What was the behavior before? Steve -- Where did you get that preposterous hypothesis? Did Steve tell you that? --- The Hiphopopotamus
- Previous message: [Python-Dev] argparse ambiguity handling
- Next message: [Python-Dev] argparse ambiguity handling
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list