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 martin.panter
Recipients Julien Baley, docs@python, georg.brandl, martin.panter, paul.j3, r.david.murray
Date 2016-01-28.22:06:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1454018777.89.0.383535198063.issue25314@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2016-01-28 22:06:17martin.pantersetrecipients: + martin.panter, georg.brandl, r.david.murray, docs@python, paul.j3, Julien Baley
2016-01-28 22:06:17martin.pantersetmessageid: <1454018777.89.0.383535198063.issue25314@psf.upfronthosting.co.za>
2016-01-28 22:06:17martin.panterlinkissue25314 messages
2016-01-28 22:06:17martin.pantercreate