mirror of
https://github.com/python/cpython.git
synced 2025-08-03 00:23:06 +00:00
GH-101111: Disambigaute origin of const for store_const and append_const (#101121)
While the documentation for `optparse` mentioned that both `store_const` and `append_const` store a constant value, it was not clear where this value was coming from. A link to `Option.const` makes this explicit.
This commit is contained in:
parent
61f338a005
commit
9a155138c5
1 changed files with 3 additions and 3 deletions
|
@ -404,7 +404,7 @@ Other actions
|
|||
Some other actions supported by :mod:`optparse` are:
|
||||
|
||||
``"store_const"``
|
||||
store a constant value
|
||||
store a constant value, pre-set via :attr:`Option.const`
|
||||
|
||||
``"append"``
|
||||
append this option's argument to a list
|
||||
|
@ -925,7 +925,7 @@ The canonical way to create an :class:`Option` instance is with the
|
|||
store this option's argument (default)
|
||||
|
||||
``"store_const"``
|
||||
store a constant value
|
||||
store a constant value, pre-set via :attr:`Option.const`
|
||||
|
||||
``"store_true"``
|
||||
store ``True``
|
||||
|
@ -937,7 +937,7 @@ The canonical way to create an :class:`Option` instance is with the
|
|||
append this option's argument to a list
|
||||
|
||||
``"append_const"``
|
||||
append a constant value to a list
|
||||
append a constant value to a list, pre-set via :attr:`Option.const`
|
||||
|
||||
``"count"``
|
||||
increment a counter by one
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue