[stdlib-sig] should we try to add argparse?
ronaldoussoren at mac.com
Sun Sep 13 09:31:03 CEST 2009
On 10 Sep, 2009, at 23:25, Benjamin Peterson wrote:
> 2009/9/10 Michael Foord <michael at voidspace.org.uk>:
>> Antoine Pitrou wrote:
>>>> Upfront people need to realize that we might have three argument
>>>> parsing libraries for a while, but it won't be forever. If we get
>>>> argparse accepted we would slowly deprecate at least optparse, if
>>>> getopt (lat time I tried to ditch getopt for Python 3 some argued
>>>> getopt supported stuff optparse didn't),
>>> +0 on deprecating getopt, -1 on deprecating optparse. Breaking a
>>> perfectly functional and useful module is stupid.
>> So we're stuck with inferior technology?
> No, that's never been the case. Download and install argparse.
optparse's source code isn't cast in stone, therefore its interface
I'm -0 on deprecating getopt, -1 on deprecating optparse and -0 on
adding argparse as is.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2224 bytes
Desc: not available
More information about the stdlib-sig