On Wed, Apr 21, 2010 at 2:14 AM, Jon Ribbens
wrote:
> On Wed, Apr 21, 2010 at 03:53:16AM -0400, Eric Smith wrote:
>> I agree the new behavior is desirable. And I also think it should be the
>> default, although I feel less strongly about that.
>>
>> But since this behavior seems to be an accident
On Wed, Apr 21, 2010 at 03:53:16AM -0400, Eric Smith wrote:
> I agree the new behavior is desirable. And I also think it should be the
> default, although I feel less strongly about that.
>
> But since this behavior seems to be an accident of the implementation
> (based on Steve's comment above
Cameron Simpson wrote:
On 20Apr2010 15:27, Neal Becker wrote:
| Steven Bethard wrote:
|
| > On Tue, Apr 20, 2010 at 11:55 AM, Neal Becker 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
On 20Apr2010 15:27, Neal Becker wrote:
| Steven Bethard wrote:
|
| > On Tue, Apr 20, 2010 at 11:55 AM, Neal Becker 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
On Tue, Apr 20, 2010 at 03:27:53PM -0400, Neal Becker wrote:
> I have a preference to allow at least exact matches to succeed even in the
> case of ambiguity - mainly because I accidentally created this already once,
> and I feel it's better to at least work somewhat. Not sure if there is any
>
At 03:27 PM 4/20/2010 -0400, Neal Becker wrote:
I have a preference to allow at least exact matches to succeed even in the
case of ambiguity - mainly because I accidentally created this already once,
and I feel it's better to at least work somewhat. Not sure if there is any
more elegant solution
Steven Bethard wrote:
> On Tue, Apr 20, 2010 at 11:55 AM, Neal Becker 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
On Tue, Apr 20, 2010 at 11:55 AM, Neal Becker 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
