[Python-Dev] argparse ambiguity handling
Jon Ribbens
jon+python-dev at unequivocal.co.uk
Wed Apr 21 11:14:39 CEST 2010
More information about the Python-Dev mailing list
Wed Apr 21 11:14:39 CEST 2010
- Previous message: [Python-Dev] argparse ambiguity handling
- Next message: [Python-Dev] argparse ambiguity handling
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 think a test should be added for it > if it's accepted as a Good Thing (tm). Otherwise it's possible that it > will vanish as the implementation changes. +1 to all of that
- 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