[ python-Bugs-1449311 ] optparse: extending actions missing ALWAYS_TYPED_ACTIONS
SourceForge.net
noreply at sourceforge.net
Sat Jun 10 18:40:39 CEST 2006
Bugs item #1449311, was opened at 2006-03-13 21:07
Message generated for change (Comment added) made by gward
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1449311&group_id=5470
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Documentation
Group: Python 2.4
Status: Open
Resolution: None
Priority: 5
Submitted By: Christopher (chrism1)
Assigned to: Greg Ward (gward)
Summary: optparse: extending actions missing ALWAYS_TYPED_ACTIONS
Initial Comment:
http://docs.python.org/lib/optparse-adding-new-actions.
html
This page of docs should include the ALWAYS_TYPED_
ACTIONS list from optparse.py. In the example, unless
you add the following line:
ALWAYS_TYPED_ACTIONS = Option.ALWAYS_TYPED_ACTIONS
+ ("dict",)
, then the "Value" variable gets no value unless you
explicitly pass "type='string'" to parser.add_option().
----------------------------------------------------------------------
>Comment By: Greg Ward (gward)
Date: 2006-06-10 12:40
Message:
Logged In: YES
user_id=14422
Oops! Quite right. Thanks for catching this.
This is actually a bug in Optik's documentation, so the real
fix is there (rev 517 of Optik svn).
Fixed in Python svn: rev 46821 (Doc/lib/liboptparse.tex).
This is trunk (Python 2.5) only.
(BTW, you forgot to mention which example had this error.
Also, the new action in the example is "extend", not
"dict". This would have been a bit quicker and easier to
fix if those details had been there.)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1449311&group_id=5470
More information about the Python-bugs-list
mailing list