This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: optparse documentation example
Type: behavior Stage:
Components: Documentation Versions: Python 3.0, Python 3.1, Python 2.7, Python 2.6
process
Status: closed Resolution: works for me
Dependencies: Superseder:
Assigned To: georg.brandl Nosy List: georg.brandl, orsenthil
Priority: normal Keywords:

Created on 2009-02-16 10:17 by orsenthil, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (3)
msg82229 - (view) Author: Senthil Kumaran (orsenthil) * (Python committer) Date: 2009-02-16 10:17
In the Document, : Doc/library/optparse.rst,
The first usage example is given with an '=' sign for the options. This
is a mistake.
 
-   <yourscript> --file=outfile -q
+   <yourscript> --file outfile -q
msg82230 - (view) Author: Senthil Kumaran (orsenthil) * (Python committer) Date: 2009-02-16 11:13
Georg, Ignore this bug. This is Invalid and  sorry for the confusion.
I was trying with single option with '=' sign.

May be, I have forgotten the Unix standard that '=' symbol goes with
'--' options only.

If other people also get confused by this, may be the following sentence
can be added, otherwise just close this bug as Invalid.

" The '=' sign after the argument goes along with '--' options only.
This is well indicated by the help message of optparse. "
msg82396 - (view) Author: Georg Brandl (georg.brandl) * (Python committer) Date: 2009-02-18 00:28
This is documented in the small glossary in the optparse docs.
History
Date User Action Args
2022-04-11 14:56:45adminsetgithub: 49528
2009-02-18 00:28:15georg.brandlsetstatus: open -> closed
resolution: works for me
messages: + msg82396
2009-02-16 11:13:11orsenthilsetmessages: + msg82230
2009-02-16 10:17:52orsenthilcreate