Cameron Simpson wrote:
On 20Apr2010 15:27, Neal Becker ndbeck...@gmail.com wrote:
| Steven Bethard wrote:
|
| On Tue, Apr 20, 2010 at 11:55 AM, Neal Becker ndbeck...@gmail.com wrote:
| I've noticed argparse ambiguity handling has changed a bit over last few
| revisions.
|
| I have cases
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), I
On Wed, Apr 21, 2010 at 2:14 AM, Jon Ribbens
jon+python-...@unequivocal.co.uk 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
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
On Tue, Apr 20, 2010 at 11:55 AM, Neal Becker ndbeck...@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:
Steven Bethard wrote:
On Tue, Apr 20, 2010 at 11:55 AM, Neal Becker ndbeck...@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
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
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
On 20Apr2010 15:27, Neal Becker ndbeck...@gmail.com wrote:
| Steven Bethard wrote:
|
| On Tue, Apr 20, 2010 at 11:55 AM, Neal Becker ndbeck...@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
