Message259164
I definitely agree with removing the remark about the “const” value with store_const. People here seem to be overloading the terms “default” and “argument”. When using store_const, it seems the programmer must also specify a value for the “const” parameter to add_argument(). It is incorrect to say it is None if not explicitly set.
On the other hand, I think if the end user omits a CLI argument configured with store_const, then the argparse module will substitute None, or the value of the “default” parameter to add_argument().
For the original report about store_true/false, perhapse it would be sufficient to port revision 49677cc6d83a to Python 3. Although there is a stray “using” that should probably be fixed. |
|
Date |
User |
Action |
Args |
2016-01-28 22:06:17 | martin.panter | set | recipients:
+ martin.panter, georg.brandl, r.david.murray, docs@python, paul.j3, Julien Baley |
2016-01-28 22:06:17 | martin.panter | set | messageid: <1454018777.89.0.383535198063.issue25314@psf.upfronthosting.co.za> |
2016-01-28 22:06:17 | martin.panter | link | issue25314 messages |
2016-01-28 22:06:17 | martin.panter | create | |
|