Message89960
> This is an edited-down excerpt form the optparse documentation from:
>
> http://docs.python.org/library/optparse.html
>
> "... the traditional Unix syntax is a hyphen (“-“) followed by a
> single letter [...] Some other option syntaxes that the world has seen
include:
> * a hyphen followed by a few letters, e.g. "-pf" [...]
Note that the second "[...]" expands to "(this is *not* the same as
multiple options merged into a single argument)". Which means:
1) optparse *does* implement the traditional Unix option-munging that
has been around since at least the mid-1980s
2) the proposed statement "optparse has chosen to implement a subset of
the GNU coding standard's command line interface guidelines, allowing
for both long and short options, but not the POSIX-style concatenation
of short options." is false
Offhand, I don't see a way for the documentation to be any clearer.
Maybe an example of "-a" and "-b" munged to "-ab"? |
|
Date |
User |
Action |
Args |
2009-07-01 00:43:59 | gward | set | recipients:
+ gward, georg.brandl, ajs |
2009-07-01 00:43:58 | gward | set | messageid: <1246409038.75.0.520763745593.issue5555@psf.upfronthosting.co.za> |
2009-07-01 00:43:56 | gward | link | issue5555 messages |
2009-07-01 00:43:55 | gward | create | |
|