[stdlib-sig] should we try to add argparse?
theller at ctypes.org
Thu Sep 10 21:59:27 CEST 2009
Brett Cannon schrieb:
> 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 not
> getopt (lat time I tried to ditch getopt for Python 3 some argued that
> getopt supported stuff optparse didn't), out of the standard library
> and toss them into PyPI for those who refuse to switch. The standard
> library might not evolve a lot, but it isn't dead or in stone.
> But before this can happen, people need to have a general consensus
> that I should bug Steven about contributing as it will require a PEP
> from him. Steven already has commit privileges to maintenance from him
> will not be a problem.
> So if you want this to actually happen and for me to start talking to
> Steven just reply to this email w/ a vote.
> I am +0
I have not used argparse, but I am missing a feature that is needed
on Windows: It should be possible to mark option flags
not only with a '-' sign (or a '--' sign) but also with a '/' sign,
plus it should be possible to have case-insensitive parsing of option
names. So that '-regserver', '/regserver' and '/RegServer' all
mean the same thing.
Does argparse allow this?
More information about the stdlib-sig