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.

Author mgedmin
Recipients georg.brandl, mgedmin
Date 2009-04-07.16:01:25
SpamBayes Score 1.8618156e-09
Marked as misclassified No
Message-id <1239120087.77.0.885148880477.issue5719@psf.upfronthosting.co.za>
In-reply-to
Content
Please add a simple usage example to the module docstring in
optparse.py.  The example available in the Python library reference
would suffice (see http://python.org/doc/current/library/optparse.html).

Rationale: optparse is convenient, but a bit unintuitive.  As a single
data point, it took me a couple of years until I started remembering the
syntax without having to refer to the documentation (compare this with,
e.g. the csv module which you'll remember how to use after reading the
docs once).  Intuitively I always typed pydoc optparse in a terminal
window and was disappointed with the lack of examples.  The online docs
are good, but not as easy to reach as pydoc.

In my experience, it's quite often that when you reach for optparse
you're alreay shaving a yak (solving a problem needed to solve the real
problem), and the five extra mouse clicks needed to find optparse's docs
in the browser are rather disruptive.
History
Date User Action Args
2009-04-07 16:01:28mgedminsetrecipients: + mgedmin, georg.brandl
2009-04-07 16:01:27mgedminsetmessageid: <1239120087.77.0.885148880477.issue5719@psf.upfronthosting.co.za>
2009-04-07 16:01:26mgedminlinkissue5719 messages
2009-04-07 16:01:25mgedmincreate