From: Moshe Zadka <moshez@math.huji.ac.il>
Date: Wed, 11 Apr 2001 07:33:08 +0000 (+0000)
Subject: Fixing bug 405999 -- clarifying differences between Python's
X-Git-Tag: v2.1c1~101
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=2bd0d88360ebc1c2ca8346891a3b4ab62a8270d4;p=thirdparty%2FPython%2Fcpython.git

Fixing bug 405999 -- clarifying differences between Python's
getopt and GNU getopt -- Python is like classical UNIX getopt.
---

diff --git a/Doc/lib/libgetopt.tex b/Doc/lib/libgetopt.tex
index 563460b30b55..c96c3cfff4a0 100644
--- a/Doc/lib/libgetopt.tex
+++ b/Doc/lib/libgetopt.tex
@@ -25,6 +25,10 @@ recognize, with options that require an argument followed by a colon
 (\character{:}; i.e., the same format that \UNIX{}
 \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
 names of the long options which should be supported.  The leading
 \code{'-}\code{-'} characters should not be included in the option