mirror of
https://github.com/python/cpython.git
synced 2025-11-11 14:44:57 +00:00
Fixing bug 405999 -- clarifying differences between Python's
getopt and GNU getopt -- Python is like classical UNIX getopt.
This commit is contained in:
parent
5d6e402e0c
commit
2bd0d88360
1 changed files with 4 additions and 0 deletions
|
|
@ -25,6 +25,10 @@ recognize, with options that require an argument followed by a colon
|
||||||
(\character{:}; i.e., the same format that \UNIX{}
|
(\character{:}; i.e., the same format that \UNIX{}
|
||||||
\cfunction{getopt()} uses).
|
\cfunction{getopt()} uses).
|
||||||
|
|
||||||
|
\strong{Note:} Unlike GNU \cfunction{getopt()}, after a non-option
|
||||||
|
argument, all further arguments are considered also non-options.
|
||||||
|
This is similar to the way non-GNU \UNIX{} systems work.
|
||||||
|
|
||||||
\var{long_options}, if specified, must be a list of strings with the
|
\var{long_options}, if specified, must be a list of strings with the
|
||||||
names of the long options which should be supported. The leading
|
names of the long options which should be supported. The leading
|
||||||
\code{'-}\code{-'} characters should not be included in the option
|
\code{'-}\code{-'} characters should not be included in the option
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue