Rietveld Code Review Tool
Help | Bug tracker | Discussion group | Source code | Sign in
(167610)

#17462: argparse FAQ: how it is different from optparse

Can't Edit
Can't Publish+Mail
Start Review
Created:
5 years, 9 months ago by techtonik
Modified:
5 years, 9 months ago
Reviewers:
merwok
CC:
rhettinger, bethard, techtonik, ezio.melotti, eric.araujo, asvetlov, docs_python.org, tshepang, devnull_psf.upfronthosting.co.za, berkerpeksag, Anastasia.Filatova
Visibility:
Public.

Patch Set 1 #

Total comments: 1

Patch Set 2 #

Patch Set 3 #

Unified diffs Side-by-side diffs Delta from patch set Stats Patch
Doc/library/argparse.rst View 1 2 1 chunk +10 lines, -0 lines 0 comments Download

Messages

Total messages: 2
techtonik
http://bugs.python.org/review/17462/diff/11350/Doc/library/argparse.rst File Doc/library/argparse.rst (right): http://bugs.python.org/review/17462/diff/11350/Doc/library/argparse.rst#newcode1892 Doc/library/argparse.rst:1892: * Providing a much simpler interface for custom ``type`` ...
5 years, 9 months ago #1
eric.araujo
5 years, 9 months ago #2
Not really, this list was copied from the argparse documentation (in the
StackOverflow response: “argparse is better for all the reasons listed on its
original page (http://code.google.com/p/argparse/)”).

This doc was written by argparse’s author, who is a Python core developer and
signed a contributor agreement for argparse code, docs and tests.  We can safely
include this patch.
Sign in to reply to this message.

RSS Feeds Recent Issues | This issue
This is Rietveld 894c83f36cb7+