optparse documentation example

[orsenthil]

BPO	5278
Nosy	@birkenfeld, @orsenthil

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/birkenfeld'
closed_at = <Date 2009-02-18.00:28:15.638>
created_at = <Date 2009-02-16.10:17:52.505>
labels = ['type-bug', 'docs']
title = 'optparse documentation example'
updated_at = <Date 2009-02-18.00:28:15.637>
user = 'https://github.com/orsenthil'

bugs.python.org fields:

activity = <Date 2009-02-18.00:28:15.637>
actor = 'georg.brandl'
assignee = 'georg.brandl'
closed = True
closed_date = <Date 2009-02-18.00:28:15.638>
closer = 'georg.brandl'
components = ['Documentation']
creation = <Date 2009-02-16.10:17:52.505>
creator = 'orsenthil'
dependencies = []
files = []
hgrepos = []
issue_num = 5278
keywords = []
message_count = 3.0
messages = ['82229', '82230', '82396']
nosy_count = 2.0
nosy_names = ['georg.brandl', 'orsenthil']
pr_nums = []
priority = 'normal'
resolution = 'works for me'
stage = None
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue5278'
versions = ['Python 2.6', 'Python 3.0', 'Python 3.1', 'Python 2.7']

[orsenthil]

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

[orsenthil]

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. "

[birkenfeld]

This is documented in the small glossary in the optparse docs.