[Python-Dev] PEP 389: argparse - new command line parsing module
Floris Bruynooghe
floris.bruynooghe at gmail.com
Mon Sep 28 17:54:52 CEST 2009
More information about the Python-Dev mailing list
Mon Sep 28 17:54:52 CEST 2009
- Previous message: [Python-Dev] PEP 389: argparse - new command line parsing module
- Next message: [Python-Dev] PEP 389: argparse - new command line parsing module
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Sep 28, 2009 at 07:28:39AM -0700, Steven Bethard wrote: > Ok, sounds like there are a number of supporters for keeping getopt > around and just deprecating optparse. For those who'd like to keep > getopt around, I have a few questions: > > * Would you be opposed to a note in the getopt documentation > suggesting argparse as an alternative? No, I'd encourage such a note. > * Would you like argparse to grow an add_getopt_arguments method (as > in my other post)? That looks nice indeed. > * If argparse grew an add_getopt_arguments, would you still want to > keep getopt around? And if so, why? If clearly documented as "Hey, getopt users, check this out!" then I'd be indifferent to the proposed deprecation of getopt. Regards Floris
- Previous message: [Python-Dev] PEP 389: argparse - new command line parsing module
- Next message: [Python-Dev] PEP 389: argparse - new command line parsing module
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list